A multi-link automatic management method and system for real estate property public funds

Abstract

The application discloses a kind of multi-link automation management method and system for real estate property public fund.It is difficult to supervise and audit complicated for the technical problems of unclear account in existing property management, the application constructs the complete link state machine of " deliberation-contract-payment-bank flow statement-reconciliation-publicity-supervision-enforcement".The system generates contract triggered by meeting resolution, obtains real flow by bank-enterprise direct connection, and establishes "three-source consistency automatic reconciliation model" of contract, income and expenditure behavior and bank flow by AI technology.The application realizes the whole-chain closed-loop management of public fund from decision source to administrative enforcement, ensures the legality, transparency and traceability of fund management.The system supports multi-level supervision and automatic early warning of abnormal account, can automatically generate administrative enforcement evidence package, and effectively solves the problem of lack of supervision means in real estate property public fund management.

Description

Technical Field

[0001] The present invention discloses a multi-link automated management method and system for the governance of public funds of real estate properties.

[0002] The present invention is applicable to the housing and urban-rural construction competent department (Housing and Construction Bureau), banks, sub-district offices, community neighborhood committees, community autonomous management organizations (owners' committees or temporary management committees), the owners themselves, and their authorized agents. Background Art

[0003] The public funds of real estate properties (with the land red line map as the management boundary, including the public housing maintenance funds (commonly known as the large fund), the daily public maintenance funds (commonly known as the small fund)), the public revenues generated from the operation of the public areas in the community, etc.) legally belong to all the owners jointly, have the attribute of common property, and are not the operating income of property companies. However, in long-term practice, the management of such funds generally has the governance pain points of "unclear accounts, unclear processes, and difficult supervision", and lacks a unified digital governance system.

[0004] Most of the existing property management information systems only cover a certain organization or a single link, such as the voting software for the owners' assembly, the property fee collection system, the contract management system, the publicity and announcement system, etc. Due to the fragmentation of the systems, it is difficult to form a closed-loop governance structure covering "deliberation - contract - payment - bank statement - reconciliation - publicity - supervision", resulting in the following technical problems that cannot be solved: (1) The governance links are fragmented and cannot be automatically connected: The link status synchronization cannot be achieved among the links of meeting deliberation, contract signing, fund payment, bank statement, automatic reconciliation, supervision and inspection, etc. There is no automatic triggering mechanism, and it is impossible to ensure the legality, integrity, and traceability of the governance chain.

[0005] (2) It is difficult to audit public funds, and the data of contracts, revenue and expenditure authorizations, and actual bank statements cannot be automatically associated: Whether the contract is signed after a legal process, whether the payment voucher corresponds to the contract terms, whether the bank statement truly reflects the contract execution situation, etc. These key data are difficult to be automatically compared by the system, and the administrative department's supervision completely relies on manual auditing, with low efficiency and easy omission.

[0006] (3) There is a lack of technical means for multi-level supervision, and it is impossible to view abnormalities in real time, resulting in continuous owner complaints: As the legal supervision entities, the Housing and Construction Bureau, the district housing and construction department, the sub-district office, and the community cannot master the public fund usage link in real time. Property companies and owners' committees violate the legal processes and misuse public funds to infringe on the rights and interests of owners, while the competent department cannot quickly and effectively identify abnormal accounts and responsible entities.

[0007] (iv) Existing systems cannot support autonomous organizations in fulfilling their statutory duties: Because current software systems on the market can only support partial transaction management, they cannot support owners' meetings, owners' committees, and temporary management committees in making decisions, publicizing information, managing contracts, managing finances, and coordinating supervision in accordance with the law. Administrative units (housing and construction, streets, communities) also lack effective information technology, resulting in the failure to form an efficient closed-loop management in a timely manner based on the rights and responsibilities listed in laws and regulations.

[0008] (v) Real estate public funds (public maintenance fund, public revenue fund) legally belong to all owners. The regulations authorize the owners' committee to collect and manage them. However, from national laws to local regulations, there has never been an authorization for property service companies to collect them. For a long time, administrative regulatory departments have defaulted to having property companies collect them before reporting to the owners' committee for liquidation. This unclear supervision and management has led to unclear accounts of public funds.

[0009] In summary, there is an urgent need for a public funds governance system that can achieve cross-organizational, cross-process, and cross-regulatory levels, so that public funds can form an automatically connected, unskippable, and fully traceable technical system from decision-making, contracts, payments, bank statements, reconciliation, public disclosure to administrative supervision. Summary of the Invention

[0010] To address the aforementioned technical challenges, this invention constructs a fully automated, end-to-end governance system for the management of public funds in the real estate sector. Internally, the system forms a complete chain: "meeting deliberation—legal resolution—contract generation—statutory public disclosure—payment events—real bank statements—automatic reconciliation of three sources—multi-level supervision—administrative enforcement." This ensures that every income and expenditure of public funds is within a continuous, unskippable, irreversible, and technically verifiable governance path, achieving authenticity, transparency, verifiability, auditability, and accountability throughout the entire process of public fund governance from its source to supervision.

[0011] It pioneered the "link governance state machine" technology, which follows a complete sequence of "meeting review - contract signing - revenue payment - actual bank transaction - automatic reconciliation - automatic public disclosure - administrative supervision - administrative enforcement." This technology enables multiple units and organizations to view the status of each link in real time according to their responsibilities, and to conduct authenticity and technical supervision of the event results and key content generated by each link.

[0012] This system pioneered a "three-source consistency automatic reconciliation model" that utilizes artificial intelligence (AI) technology to analyze three core data sources: contract amounts and rule terms, compare actual income and expenditure, and verify bank transaction records. Through comprehensive matching of multi-dimensional data, including amount characteristics, time windows, transaction partners, and AI analysis of specific contract terms, the system automatically verifies the reconciliation process. It efficiently distinguishes between normal and abnormal income and expenditure, providing reliable technical evidence for regulatory authorities, self-governing organizations, and property owners, significantly improving the accuracy and timeliness of public fund reconciliation.

[0013] The system supports both owner assembly deliberation and owner committee meeting deliberation. The system automatically verifies the voting ratio, area ratio, and whether the public announcement has been completed. Only after the deliberation results are legal and valid and the legally required public announcement has been completed will the contract be allowed to enter the contract chain, ensuring that the triggering source of the contract chain is legal, valid, and traceable.

[0014] The system supports automatic disclosure of links, automatically generating legally required disclosure content related to contracts, payments, and reconciliation based on the link status, ensuring the right to know for owners and competent administrative departments.

[0015] By obtaining actual bank account transaction records and receipts through direct bank-enterprise connections or financial interfaces, the complete authenticity of account fund transactions can be verified.

[0016] It supports real-time, permission-based monitoring of regulatory bodies such as municipal and district housing and construction bureaus, street offices, and communities, as well as monitoring of abnormal accounts and contract execution.

[0017] It supports early warning of abnormal accounts and allows multiple levels of regulatory departments to jointly supervise and rectify them, avoiding situations where there is poor communication between different regulatory departments. After correction, it automatically triggers reconciliation and public disclosure again.

[0018] It supports administrative law enforcement support links and automatically generates law enforcement evidence packages containing resolutions, contracts, payments, transaction records, and abnormal records, quickly forming evidence recognized by judicial units.

[0019] Build a unified data structure model to enable automatic association of multi-source data such as contracts, payments, and bank statements across links.

[0020] It supports automatic triggering, sequential execution, parallel execution, or asynchronous execution of link modules, enabling the system to be scalable and preventing evasion behavior.

[0021] Compared with existing technologies, this invention supports multiple functions such as data structure, triggering mechanism, state management, matching algorithm, authenticity archiving and traceability, and generation of law enforcement evidence chain. It has significant novelty, inventiveness and practicality, and can promote the improvement of social governance efficiency and economic value, which is in line with the overall direction of the national "15th Five-Year Plan" for the construction of Digital China.

[0022] To achieve the above functions, the present invention adopts the following core technical solutions: (a) Link State Machine Technology This invention automatically connects the review chain, contract chain, public disclosure chain, payment chain, bank transaction chain, reconciliation chain (including AI analysis of contract content), regulatory chain, and enforcement chain in a fixed order. The next chain cannot be entered until any link is completed, ensuring that the governance path is legal, complete, unskippable, and fully traceable.

[0023] (II) Three-Source Consistency Reconciliation Model This invention pioneers a "three-source consistency automatic reconciliation model" based on three core data sources: legally effective contract terms, actual income and expenditure transactions, and genuine bank transaction records. By identifying transaction partners, amount characteristics, and time windows in bank transaction records, and using AI technology to analyze contract payment terms, the system achieves automatic verification of the reconciliation process. The system can efficiently distinguish between normal and abnormal income and expenditure, providing reliable technical evidence for regulatory authorities, self-governing organizations, and property owners, significantly improving the accuracy and timeliness of public fund reconciliation.

[0024] (III) Public disclosure of the mandatory chain mechanism Contracts, income and expenditure, major events, and public disclosure materials must all be entered into the disclosure chain. If the required disclosure is not completed, the materials cannot enter the payment chain, thus ensuring the legality of the procedures, the completeness of the process, and the transparency of the information from a technical perspective.

[0025] (iv) Multi-level regulatory system This invention provides a real-time governance view to the municipal housing and construction bureau, district housing and construction bureau, sub-district office, and community through a regulatory chain, enabling full supervision of the contract chain, payment chain, reconciliation chain, and publicity chain, and can automatically issue early warnings for abnormal accounts, forming a closed loop of responsibility chain.

[0026] (v) Generation of evidence chain for administrative law enforcement The system automatically integrates review chains, contract chains, payment chains, bank transaction chains, reconciliation chains, and rectification records to generate a structured and downloadable administrative law enforcement evidence package, providing credible evidence chains that can be directly used by housing and construction law enforcement, discipline inspection and supervision, and auditing departments.

[0027] (vi) Scope of application This invention can be widely applied to real estate properties such as residential communities, mixed-use buildings, office buildings, commercial plazas, and industrial parks, and is suitable for professional management of public funds. It has high replicability and city-level promotion value.

[0028] (vii) Reviewing the legitimacy chain of protection The system supports both general meetings of owners and meetings of the owners' committee for deliberation. The system automatically verifies the legally required voting ratio, exclusive area ratio, and whether the public announcement has been completed for different meetings. Only after the deliberation results are legal and valid and the legally required public announcement has been completed will the contract be allowed to enter the contract chain, ensuring that the triggering source of the contract chain is legal, valid, and traceable.

[0029] (viii) The originality of link governance state machine technology This invention pioneered a link governance state machine technology with a complete sequence of "meeting review - contract signing - revenue payment - actual bank transactions - automatic reconciliation (using artificial intelligence AI to analyze contract terms) - automatic public disclosure - administrative supervision - administrative enforcement". This technology enables multiple units and organizations to view the status of public funds links in real time and to conduct full-process technical supervision of the authenticity of the elements generated by each link.

[0030] This invention, through a full-chain governance framework, has for the first time achieved a comprehensive improvement in the management of public funds for real estate in five dimensions: "legality, transparency, accuracy, regulatory oversight, and law enforcement," at the technical system level, and has significant social governance and livelihood value. Attached Figure Description

[0031] Figure 1 This is a schematic diagram of the overall system architecture of the present invention, showing the modules: M1 (Meeting Resolution Link); M2 (Contract Link); M3 (Payment Link); M4 (Bank Link); M5 (Automatic Reconciliation of Three Sources); M6 (Automatic Publication Link); M7 (Multi-level regulatory link: Municipal Housing and Construction Bureau → District Housing and Construction Bureau → Sub-district Office → Community, where information about the communities under its jurisdiction can be viewed). Interaction relationships of M8 (Administrative Law Enforcement Auxiliary Link).

[0032] Figure 2 This is a flowchart of the meeting resolution (deliberation) process of this invention, following these steps: S101 (Topics that can be initiated by the owners' meeting / owners' committee). S102 (Vote at the owners' meeting or the owners' committee meeting). S103 (Forming the final resolution of the owners' assembly or owners' committee meeting). S104 (The contents of the meeting resolutions shall be publicized to the owners. According to the rules of procedure of the owners' meeting, the publicity period is generally 3-7 days). S105 (After the public notice period expires and no valid objections are raised, the resolution becomes effective and is documented).

[0033] Figure 3 This is a schematic diagram of the contract chain process of the present invention, including: C201 (pursuant to the effective resolution); C202 (Generate Contract Node); C203 (Contract with official seal and public notice); C204 (Listed in a planned status of pending payment or pending collection).

[0034] Figure 4 This is a schematic diagram of the payment and collection process of the present invention, including: P301 (Contract enters executable status, payment application submitted). P302 (The owners' committee meeting decides whether to approve the application); P303 (Payment executed, added to the queue of events pending automatic reconciliation).

[0035] Figure 5 This is a schematic diagram of the bank statement acquisition process of the present invention (direct bank-enterprise connection), including: B401 (Access to external financial account API interface); B402 (Bank returns account transaction data); B403 (Write to the "Bank Transaction Data Table" in the database of this system).

[0036] Figure 6 This is a schematic diagram of the automatic reconciliation process for three-source consistency of the present invention, showing: Source D1 (Amount receipts and payments requirements of contracts that have already taken effect); Source D2 (List of income or expenditure amounts and recipients approved by the owners' committee); Source D3 (actual bank transaction data, recording the recipients, amounts, and times of payments); All three sources of information are aggregated into the matching and determination function of E601 (the core reconciliation engine) to determine whether the contract terms are met.

[0037] Figure 7 This is a schematic diagram of the automatic disclosure link process of the present invention, including: G601 (Generate public notice content); G602 (Information Disclosure and Release); G603 (Evidence of the publicized content is kept on file).

[0038] Figure 8 This is a schematic diagram of the collaborative law enforcement process for handling abnormal accounts according to the present invention, including: E801 (Abnormal receipts or payments detected); E802 (The administrative regulatory unit reviewed and issued rectification requirements); E803 (Owners' Committee / Property Management Rectification and Submission of Explanation); E804 (After the administrative law enforcement unit determines that the rectification has been completed, the automatic reconciliation of the income and expenditure object or amount will be triggered again).

[0039] Figure 9 This is a schematic diagram of the multi-level regulatory structure of the present invention, showing: U1 (Municipal Housing and Construction Bureau); U2 (District-level Housing and Construction Bureau); U3 (Subdistrict Office); The hierarchical structure of U4 (Community Residents' Committee).

[0040] Figure 10 This is a schematic diagram of the administrative law enforcement auxiliary process of the present invention, including: L901 (Extract clues about violations); L902 (Generate relevant reports); L903 (sent to law enforcement agencies); L904 (Feedback on Enforcement Results). Example

[0041] The multi-link automated management method and system for public funds in real estate projects provided by the present invention will be further described below with reference to the accompanying drawings and specific embodiments. It should be understood that the following embodiments are for illustrative purposes only and are not intended to limit the scope of protection of the present invention.

[0042] like Figure 1 As shown, the public funds multi-link governance system of the present invention mainly includes: a review link module, a contract link module, a public disclosure link module, a payment and collection link module, a bank transaction link module, an automatic reconciliation link module, a multi-level supervision link module, an abnormal account collaborative processing and administrative law enforcement assistance module, a link state machine module, and an authenticity archiving module.

[0043] The system is deployed on a computer server platform, preferably on the government extranet platform, and establishes data connections with community self-governing organizations, property service companies, administrative regulatory departments, and bank accounts, building a platform account system using a real-name registration method. For each real estate project, such as residential communities, office buildings, and commercial complexes, the system establishes an independent public fund management project, unifying the project's related resolutions, contracts, daily public maintenance fund income, public revenue income, and related expenditures into a single governance framework.

[0044] At the data level, core data related to public funds are preferably categorized into the following three types: The first category is contract sources. Contract sources include public revenue operation contracts, public facility maintenance contracts, service procurement contracts, etc., legally formed by the owners' assembly or owners' committee. These records include contract number, resolution number, name of the contract counterparty, agreed amount, payment node, collection node, and account information. Furthermore, the contract source can be configured with a contract clause intelligent analysis submodule to segment and parse the uploaded or entered contract text, automatically marking key content such as payment clauses, installment payment arrangements, security deposit clauses, breach of contract liability clauses, and risk warning clauses. The recognition results are written into the contract source data structure as structured fields for use in the review process, payment and collection process, and automatic reconciliation process.

[0045] The second category is system sources. System sources include internal payment amount review records, payment event records, receipt confirmation records, invoice upload records, automatic reconciliation verification vouchers, etc., which are automatically generated by the system or confirmed online by the responsible party.

[0046] The third category is bank sources. Bank sources include the actual income and expenditure records of bank accounts such as public revenue accounts and public maintenance fund accounts opened by the owners' committee or temporary management committee. The source can be the result returned by the bank-enterprise direct connection interface, or the result of image recognition of the original bank statement.

[0047] In this embodiment, the deliberation link module is responsible for confirming the legality of the resolution; the contract link module is responsible for generating and managing contracts based on the resolution; the payment and collection link module is responsible for recording actual payment and collection activities; the bank transaction link module is responsible for obtaining real bank transaction records; the automatic reconciliation link module is responsible for performing automatic comparisons between contract sources, system sources, and bank sources; the multi-level supervision link module is responsible for displaying the link status and abnormal results to supervisory bodies at all levels; and the abnormal account collaborative processing and administrative law enforcement assistance module generates electronic evidence packages when abnormalities occur or law enforcement is required. The link state machine module runs through all business modules and provides unified control over the link status; the authenticity archiving module generates summaries of key events in each link and forms a chain-like archiving structure for post-event authenticity verification. like Figure 2 As shown, the review process is mainly applicable to the following matters: issues that require decisions on the operation, contracting, and use of public revenue; issues that require decisions on large expenditures of public maintenance funds; issues that require decisions on the signing or modification of important contracts; and issues that require confirmation of the public fund revenue and expenditure budget or final accounts.

[0048] The basic process of the review chain may include the following steps.

[0049] First, the agenda items are initiated by legitimate entities. In this embodiment, the decision-making organizations for real estate projects mainly fall into two categories: one is the owners' assembly preparatory group initiating agenda items through this system; the other is the community self-governing organization, acting as the executive body of the owners' assembly, exercising the corresponding rights representing all owners under the authorization of the owners' assembly or by laws and regulations. The system records information such as the agenda item number, initiating entity, initiation time, type of contract involved, estimated amount, and source account of funds, and writes this information into the draft node of the review process.

[0050] Secondly, the system sets pre-requisite legality parameters. Based on the existing ownership data of the real estate project, the system automatically calculates the total number of owners and the total exclusive area of ​​the owners' meeting, and pre-sets voting conditions according to laws, regulations or community management rules, such as the participation of more than two-thirds of the owners, more than half of the owners' approval, more than three-quarters of the owners' approval, or the owners' committee meeting requiring more than half of the committee members' approval, etc., as the parameter basis for automatically determining whether the review chain is legally passed.

[0051] Next, the system generates a public notice page for deliberation and organizes voting. The system can automatically generate a public notice page in the homeowner's application, displaying the topic content, voting method, and voting deadline, and allowing street and community accounts to view the public notice online. Both online and offline voting results are collected based on the homeowner's ID card information or legal representative authorization information. The system saves the voter's identity, voting time, voting option, and corresponding private area for each voting record. When the topic is a community self-governance organization contract review chain topic, the system generates an internal voting interface on the committee member's end and counts votes one vote per member, not based on private area.

[0052] After the voting deadline, the system automatically counts the number of participants, the area of ​​participation, the number of votes in favor, the number of votes against, and the number of abstentions. Based on pre-set rules, it automatically determines the outcome and writes the results to the resolution node in the deliberation process. When the voting meets the passing conditions, the system generates a resolution record with a unique number, including the topic content, the method of passage, the voting result, the scope of application, and the identifier of any contracts that need to be signed or amended. This resolution number will serve as the sole legitimate trigger for the contract process. When creating review topics, this system marks the topic type as either "Owners' Meeting Review Chain Topic" or "Community Self-Governing Organization Contract Review Chain Topic." The Owners' Meeting Review Chain primarily reviews whether to make a certain decision, such as whether to replace the elevator, whether to agree to a certain public revenue management model, or whether to authorize the signing of contracts within a certain monetary limit.

[0053] Regarding the matters to be considered at the owners' meeting, let's assume: The total number of owners is: total number of owners; The total area owned by all owners is: total area; The number of homeowners participating in this vote is: number of participants; The total area of ​​the exclusive ownership of the owners participating in this vote is: Participating Area; The number of people corresponding to the affirmative votes in the valid votes is: the number of people in favor; The number of people who voted against the valid votes is: the number of people who voted against. The number of people who abstained from valid votes is: the number of abstentions.

[0054] The system first calculates the following three ratios: Participant percentage = Number of participants ÷ Total number of participants; Participating area ratio = Participating area ÷ Total area; Percentage of votes in favor = Number of votes in favor ÷ (Number of votes in favor + Number of votes against + Number of abstentions).

[0055] For rules requiring a minimum of half or more of both the number of attendees and the area of ​​the venue to pass, or a minimum of three-quarters or more to pass, the system pre-sets the following threshold parameters: The minimum number of participants required by law: the minimum number of participants; Statutory minimum participation area ratio: Minimum participation area; Minimum approval percentage required for a vote to pass: Minimum approval percentage.

[0056] The automatic determination rule is as follows: The resolution of the owners' meeting is deemed "passed" when all of the following conditions are met: (a) The proportion of participants is greater than or equal to the minimum number of participants; (ii) The proportion of participating area is greater than or equal to the lower limit of participating area; (iii) The percentage of votes in favor is greater than or equal to the lower limit of the percentage of votes in favor.

[0057] If any of the above conditions are not met, the resolution of the owners' meeting shall be deemed "not passed".

[0058] Furthermore, if the management regulations for a real estate project stipulate that "failure to vote is considered an abstention," then when calculating the number of participants and the area of ​​participation, the system can include the total number of owners and the total area of ​​owners in the participation base, while including the number of votes corresponding to those who did not vote in the number of abstentions and the area of ​​abstentions, and adjust the numerator and denominator in the above proportional formula accordingly. For specific contract review resolutions made by the owners' committee or temporary management committee within the scope of authorization of the owners' meeting, the system sequentially performs verification of the scope of authorization, verification of the legality of the committee members' voting, and verification of the legality of the publicity period. Assumption:

[0059] The maximum authorized amount stipulated in the relevant owners' meeting resolution is: Maximum authorized amount; The proposed contract amount is: Contract Amount; The types of authorized matters stipulated in the resolution are: Types of Authorized Matters; The type of matter to which this contract pertains is: Contract Matter Type; The authorization period stipulated in the resolution is valid from the start date of its establishment to the expiration date. The proposed signing date for this contract is: Contract Signing Date.

[0060] The system checks the following conditions: (a) Contract amount ≤ Authorized amount limit; (ii) The type of contract matter falls within the scope of authorized matters; (iii) The contract signing date falls within the time interval of [the start date of establishment to the expiration date].

[0061] If any condition is not met, the contract review is deemed to be "out of the authorized scope", the review chain status is marked as "authorization not met", and the system will not allow the generation of a contract node that can be stamped and made effective. After confirming that the contract review is within the authorized scope, the system determines the legality of the owners' committee's internal vote based on the number of committee members and the number of attendees. Assumption:

[0062] The total number of committee members is: the total number of committee members; The actual number of committee members who participated in the voting at this meeting was: number of committee members present. The number of committee members corresponding to the affirmative votes in the valid votes is: the number of committee members in favor; The number of committee members who voted against the resolution in a valid vote is: the number of committee members who voted against the resolution. The number of committee members who abstained from voting in a valid vote is: the number of committee members who abstained.

[0063] System calculation: Committee attendance rate = Number of attending committee members ÷ Total number of committee members; Percentage of committee members in favor = Number of committee members in favor ÷ Total number of committee members.

[0064] According to the owners' committee charter or relevant regulations, the system is pre-configured as follows: Minimum attendance ratio of committee members: Minimum attendance ratio of committee members; Lower limit for the percentage of committee members in favor: The lower limit for the percentage of committee members in favor.

[0065] The automatic decision-making rules for internal voting are as follows: The internal review result of a specific contract is deemed "approved" when all of the following conditions are met: (i) The proportion of committee members present is greater than or equal to the minimum number of committee members present; (ii) The percentage of committee members in favor is greater than or equal to the lower limit of committee members' approval.

[0066] Otherwise, it will be judged as "not passed".

[0067] If the owners' committee charter stipulates that "members who do not express their opinion are considered to have abstained" or "members who do not vote within a certain period of time are considered to have abstained", then when the system counts the number of members who voted in favor, the number of members who voted against, and the number of members who abstained, the members who did not vote within the specified period will be included in the number of members who abstained, and the above-mentioned proportion of members who voted in favor will be calculated accordingly. After being reviewed and approved by the owners' committee, the system automatically enters the legality verification stage during the public notice period. Only after completing the legally mandated or agreed-upon public notice procedures can the resolution enter the "can be sealed and take effect" state.

[0068] Assumption: The minimum number of days for public announcement is the lower limit of the number of days for public announcement; The actual number of days the resolution on this contract review was publicly displayed is: actual number of days displayed. The number of valid objections recorded by the system during the public announcement period is: number of valid objections; The number of objections that have been processed and re-approved during the public notice period is: number of objections processed.

[0069] The system's rules for determining the legality of the public notice period are as follows: (i) The actual number of days of public notice is greater than or equal to the lower limit of the number of days of public notice; (ii) The number of valid objections is 0, or the number of valid objections is equal to the number of objections that have been processed, and the result of the re-examination of the content involved in the objection is "passed".

[0070] If all of the above conditions are met, the contract review resolution is legally valid based on its internal voting; otherwise, the system will mark the contract review status as "unresolved objections exist during the publicity period," and will not allow it to enter the "effective" status in the contract chain, nor will it allow the final official seal to be affixed to the contract text. Regarding the owners' committee's review of specific contracts, the system makes a final judgment based on the following comprehensive rules:

[0071] If both conditions are met: (a) The authorization scope verification passed; (ii) The conditions for the legality of the committee members' vote are met; (iii) The legality conditions for the public notice period have been met; If the system determines that the owners' committee's review of the specific contract is "passed and effective", a review node is generated that can serve as a legitimate trigger source for the contract and payment links; otherwise, the review node status remains "not passed" or "pending processing" and cannot be used as a legitimate source for subsequent links.

[0072] Through the above two types of parameters and formulas, this invention establishes a quantifiable legality determination mechanism for the resolutions of the owners' meeting and the review of specific contracts by the owners' committee. It constrains decision-making behavior from the entry point of the chain, ensuring that every decision-making node entering the contract chain, payment chain and reconciliation chain has a clear, traceable and publicly verified legal basis. like Figure 3 As shown, the contract chain generates and manages contract records based on the review resolutions, specifically including the generation of draft contracts, public disclosure and filing of contracts, signing and archiving of contracts, and intelligent identification and risk warning of contract terms.

[0073] First, based on the resolution, the system generates a draft contract by the authorized drafter. The contract must include key clauses such as the names of the contracting parties, the subject matter, the amount, payment methods, account information, performance period, and breach of contract clauses. When members of the owners' committee have objections to the contract, they can vote against it and note their reasons, which are recorded in the system.

[0074] Secondly, after the owners' assembly or owners' committee makes a decision on a certain contract matter, the system generates a "Contract Decision Public Notice" record and publicizes the decision to all owners of the real estate project within the prescribed public notice period. Only when the public notice period expires and there are no valid objections, or when valid objections have been processed and re-approved, will the system mark the review status of the contract matter as "ready to be signed," allowing subsequent generation of contract nodes that can be stamped with an official seal and the generation of corresponding filing records on the regulatory end.

[0075] Secondly, once both parties confirm the contract terms, and the contract matter is in the "pending signing" state in the review and public disclosure chains, the authorized signatory completes the signing via electronic signature or by uploading a scanned copy of the paper document. The system binds the final contract document with the corresponding owners' meeting resolution number or owners' committee review number, generating a contract node in the contract chain. After the contract is signed, the system automatically generates a contract execution result public disclosure page for the owners of this real estate project, displaying the core information and effective status of the contract, while simultaneously generating a contract filing record on the regulatory end. Furthermore, when the contract is sealed and becomes effective, the system can also automatically send a filing email containing a summary of the review process and an image of the sealed contract document to the email address reserved by the regulatory department to complete the backup and preservation of key information. After the draft contract is generated and the final contract document is uploaded, the system automatically analyzes the entire contract text. Preferably, the system first segments the contract text by chapter, clause, and payment, converting each segment into a text fragment suitable for computer processing. Subsequently, combining a pre-set clause feature lexicon and clause pattern library, and optionally using a clause recognition algorithm trained on sample contracts, the system identifies the clause type of each fragment, labeling them as payment clauses, collection clauses, performance obligation clauses, breach of contract liability clauses, dispute resolution clauses, and risk warning clauses, and extracts the corresponding key elements, such as payment amount, payment time, payment conditions, penalty percentage, and breach triggering conditions.

[0076] In a preferred implementation, the present invention can label contract samples that have been manually reviewed and approved in historical contracts as "normal samples," and label contract samples that have been rejected, identified as having significant risks by regulatory authorities, or renegotiated by the owners' assembly as "risk samples," thus forming a clause analysis sample library. The system can iteratively train the clause recognition algorithm based on this sample library, enabling the AI ​​clause analysis module to output deviation assessments and default risk warnings for various clauses when new contracts are imported.

[0077] To facilitate the quantification of risk levels, this invention sets basic risk weights for different types of clauses. Assumptions: The risk weighting of payment terms is: payment weighting; The risk weighting of the breach of contract liability clause is: breach weighting; The risk weights for other important terms are: Other Weights.

[0078] Based on the rigor of the terms and conditions and whether there are any provisions that are clearly detrimental to all homeowners, a risk score is calculated for each type of clause. For example: Payment terms risk deduction: Payment deduction; Risk deductions for breach of contract clauses: Deductions for breach of contract; Other clause risk deductions are: other deductions.

[0079] The overall risk score of the contract terms can then be expressed as: Comprehensive risk score = 100 - (Payment weight × Payment deduction + Default weight × Default deduction + Other weights × Other deductions).

[0080] 100 is the maximum score. The more the contract terms deviate from the usual scope of fairness and prudence, the higher the corresponding risk deduction score, and the lower the overall risk score. The system can set several warning levels based on the overall risk score. For example, when the score is lower than a preset threshold, a high-risk warning will pop up on the review interface for committee members and regulators, reminding them to pay close attention to payment arrangements, liability allocation, and consequences of default during the voting process.

[0081] IV. Payment and Collection Link and Spending Consistency Algorithm (corresponding to) Figure 4 , Figure 5 ) like Figure 4 As shown, the expenditure process adds "submitting for payment review" as a prerequisite before recording actual payments. The specific steps include: The first step is that when a certain payment milestone stipulated in the contract is approaching, the owners' committee or the temporary management committee initiates a payment proposal in the system based on the specific payment terms of the contract, and fills in information such as the proposed payment amount, the planned payment time, and the account of the receiving unit.

[0082] The second step involves the system pushing the payment issue to all committee members or relevant decision-making bodies. Committee members can view the original contract, historical income and expenditure information, and other information online, and then vote. The voting results are automatically tallied by the system and form an internal payment amount review record, which includes the voting results, the percentage of approvals, the voting time, and information on the participants.

[0083] Third, the system only allows the generation of a corresponding payment event if the internal payment amount review record shows "approved" and has not expired. The payment event record includes information such as contract number, resolution number, internal review record number, proposed payment amount, payee name, and payee account, which serves as the basis for initiating subsequent bank payments.

[0084] Fourth, after the finance staff completes the payment at the bank or through the payment interface connected to the system, a corresponding outgoing record appears in the bank's transaction history. The system then automatically associates this outgoing record with the aforementioned payment event through the transaction history matching relationship.

[0085] Fifth, after payment is completed, the counterparty issues an invoice corresponding to the expenditure to the payer in accordance with the contract or financial management requirements. Financial personnel or authorized personnel upload a scanned copy, electronic invoice file, or invoice image to the system, and enter information such as the invoice number, invoice amount, invoice date, and issuer's name, thus linking the invoice record with the corresponding payment event, contract record, and bank disbursement record. Only after the invoice is uploaded will the system mark the expenditure as "invoice complete" and include it in the expenditure-side complete verification process.

[0086] For a given expenditure, record: The amount payable in this transaction as stipulated in the contract is: Contract Amount Payable; The amount recorded in the system for this payment event is: the system payment amount; The corresponding outgoing amount in the bank statement is the actual amount paid by the bank. The invoice amount associated with this expenditure is: invoice amount; The name of the payee as specified in the contract is: the name of the payee. The recipient's name recorded in the bank statement is: the name of the payee in the bank statement. The name of the invoice issuer recorded on the invoice is: Invoice Issuer Name; The planned payment date stipulated in the contract is: Planned Payment Date; The actual date of disbursement in the bank statement is the actual date of payment.

[0087] Let the allowable deviation of the amount be: amount tolerance; Let the allowable date deviation in days be: date tolerance in days.

[0088] The condition for the amounts to match is: The absolute value (contract amount payable - bank payment amount) ≤ the amount tolerance, and The absolute value (system payment amount - bank actual payment amount) ≤ the amount tolerance, and Absolute value (invoice amount - bank payment amount) ≤ Amount tolerance.

[0089] The payment time matching condition is: The actual payment date falls within the range [Planned payment date - Date tolerance days, Planned payment date + Date tolerance days] Inside.

[0090] The condition for the payee's name to match is: The name of the contract payee and the name of the payment receipt are completely identical after removing spaces, standardizing fonts, and removing common suffixes from company names. The name of the contract payee and the name of the invoice issuer are completely identical after removing spaces, standardizing the font, and removing common suffixes of company names.

[0091] Common suffixes for company names may include expressions such as "Limited Liability Company" or "Joint-Stock Company".

[0092] The conditions for an invoice to be complete are: (i) There are invoice upload records associated with this payment event; (ii) The invoice amount recorded in the invoice upload record is consistent with the system payment amount within the amount tolerance range; (iii) The contract number and payment event number pointed to by the invoice upload record are consistent with the expenditure.

[0093] The logic for determining the consistency of the three sources of this expenditure is as follows: If both conditions are met: (i) The contract amount payable, the system payment amount, the bank payment amount, and the invoice amount are consistent within the tolerance range; (ii) The actual payment date falls within the allowable deviation date range; (iii) The name of the contract payee, the name of the payment receipt, and the name of the invoice issuer are consistent; (iv) The invoice has been uploaded and linked for archiving; Then the expenditure consistency flag = consistent; Otherwise, the expenditure consistency flag is set to inconsistent.

[0094] Within a billing period, the system performs the above judgment on all expenditure records and compiles the following statistics: Total number of expenditures = Total number of expenditure records in this accounting period; Number of abnormal expenditures = Number of expenditures marked as "inconsistent" when they are consistent with each other.

[0095] Therefore, we can conclude that: The percentage of abnormal expenditures = the number of abnormal expenditures ÷ the total number of expenditures.

[0096] The proportion of abnormal expenditures can be used as one of the quantitative indicators by regulators to measure the risk level of public funds expenditures in a real estate project, and can be used by subsequent risk scoring models.

[0097] V. Revenue Recognition Chain and Revenue Consistency Algorithm (corresponding to) Figure 4 , Figure 5 ) like Figure 5 As shown, for each income transaction, this embodiment generates an internal system voucher through "bank deposit + double confirmation + invoice upload".

[0098] First, once an incoming transaction record appears in the bank transaction history, the system filters out candidate transactions that may be related to a certain contract from among numerous incoming transaction records, based on the name of the payer, the amount, or the remarks information stipulated in the contract source.

[0099] Secondly, the finance committee member logs into the system, checks the payment unit name, amount, and date in the candidate transaction list, and selects the corresponding contract terms for initial confirmation. The system generates a record containing the initial confirmer, confirmation time, and matching contract number.

[0100] Subsequently, the chairman of the owners' committee reviewed the transaction records, which had already been initially reviewed by the finance committee member, in the system. He confirmed that the amounts, payment units, and contract terms were consistent, and completed the final review after confirming everything was correct. The system generated a double confirmation record for the receipt of payment, including both confirmation actions and their times.

[0101] Finally, after revenue is confirmed, the finance staff issues an invoice to the other party according to the contract. The system records the invoice number, amount, invoice date, and name of the invoice issuer, and uploads a scanned copy of the invoice or an electronic invoice file, which is then linked to the double confirmation record of the receipt of payment.

[0102] Only when the bank deposit record, the double confirmation record of receipt, and the invoice upload record meet the consistency conditions in terms of amount and counterparty name will the system mark the income as "received and the invoice is complete" and include it in the automatic reconciliation process.

[0103] Automatic formula for determining consistency of revenue from three sources: For a given income, record: The amount receivable stipulated in the contract is: Contract Receivable Amount; The amount credited to the bank statement is the actual amount received by the bank. The amount in the double confirmation record for receipt of payment is the amount confirmed by the system. The invoice amount associated with this revenue is: invoice amount; The name of the party obligated to make payment as stipulated in the contract is: the name of the party making the payment under the contract; The payer's name recorded in the bank statement is: the name of the payer in the bank statement; The name of the invoice issuer is recorded as: the payee is the invoice issuer.

[0104] Let the allowable deviation of the amount be: amount tolerance.

[0105] The condition for the amounts to match is: The absolute value (contract receivable amount - bank actual receipt amount) ≤ amount tolerance, and The absolute value (system-confirmed amount - bank-received amount) ≤ the amount tolerance, and Absolute value (invoice amount - system confirmed amount) ≤ amount tolerance.

[0106] The condition for the payer's name to match is: The names of the payers in the contract and the names of the payers in the transaction records are identical after removing spaces and using the same font.

[0107] In a preferred embodiment, the name of the invoice issuer and the name of the contract payer are completely identical after removing spaces and unifying the font.

[0108] The conditions for double confirmation and invoice are: (i) There is one confirmation record of the finance committee member and one confirmation record of the owners' committee director, and both records point to the same bank's deposit record; (ii) There is an invoice upload record associated with the accounting entry record, and the invoice amount is consistent with the amount confirmed by the system within the amount tolerance range; (iii) The contract number pointed to by the invoice upload record is consistent with the contract number corresponding to the income.

[0109] The logic for determining the consistency of the three sources of income is as follows: If both conditions are met: (i) The contract receivable amount, the bank's actual receipt amount, the system-confirmed amount, and the invoice amount are consistent within the amount tolerance range; (ii) The name of the payer in the contract is consistent with the name of the payer in the cash flow statement; (iii) Double confirmation of receipt of payment has been completed; (iv) The invoice has been uploaded and the invoice amount matches the amount confirmed by the system; Then the income consistency flag = consistent; Otherwise, the income consistency flag is set to inconsistent.

[0110] Within a billing period, the system statistics are as follows: Total number of revenue transactions = Total number of revenue records in this accounting period; Number of income discrepancies = Number of income discrepancies marked as "inconsistent".

[0111] Therefore, we can conclude that: Abnormal revenue ratio = Number of abnormal revenue transactions ÷ Total number of revenue transactions.

[0112] The abnormal revenue ratio, together with the abnormal expenditure ratio, can be used to reflect the overall risk status of public funds for the real estate project on both the revenue and expenditure sides. like Figure 5 As shown, the bank transaction record is used to obtain the actual income and expenditure data of the public funds special account, and can be implemented in the following two ways.

[0113] The first method is direct bank-enterprise connection. The system interfaces with the bank's corporate online banking or open interface system, automatically obtaining the payment and receipt records of the public funds account at an agreed frequency. The data returned by the interface may include information such as transaction date, amount, balance, counterparty name, counterparty account number, and remarks. The system converts this into a unified data structure and then writes it into the bank's transaction record.

[0114] The second method is bank statement image recognition. For real estate projects that have not yet achieved direct bank-enterprise connection, the owners' committee can upload images of bank paper bank statements. The system uses optical character recognition technology to identify the transaction date, amount, summary, and counterparty information, and after manual random checks and confirmation, it is written into the bank's transaction record.

[0115] Through the above methods, regardless of whether direct bank-enterprise connection has been enabled, the bank transaction record can accurately reflect the actual income and expenditure of the special fund account and serve as the sole source of the bank source in this invention. like Figure 6 As shown, the automatic reconciliation link is used to perform automatic matching, consistency determination of the three sources, anomaly identification, and risk scoring calculation of all income and expenditure records during the reconciliation period among contract source, system source, and bank source. It is the key algorithm link for the present invention to realize the automated verification of public funds.

[0116] The automatic reconciliation process can perform one or more automatic reconciliations within each billing period, and its steps include the following.

[0117] First, the system prepares the data. The system extracts contract records from the contract source that are in execution and have receivables or payables clauses within the current accounting period; it extracts payment events, double confirmation records of receipts, internal payment review records, invoice records, and other business documents related to contract performance within the current accounting period from the system source; and it extracts all bank transaction records of the public funds account within the current accounting period from the bank source.

[0118] Secondly, the system executes matching rules. For expenditures, the system performs correlation matching based on contract number, contract amount due, name of the payee, planned payment date, payment event records, invoice records, and bank statements. For revenues, the system performs correlation matching based on contract number, contract amount receivable, name of the payer, double confirmation records of receipt, invoice records, and bank statements. For installment payments, installment receipts, or multiple combined payments / receipts, the system can also perform combined matching based on time windows, amount tolerances, remarks, and related entity information.

[0119] After matching is completed, the system automatically verifies each expenditure and each income transaction by applying the aforementioned three-source consistency judgment rules for expenditure and income. That is, the system marks an expenditure as "consistent" only when there are corresponding records that can be correlated in the contract source, system source, and bank source, and the conditions of consistent amount, consistent entity name, consistent time, and supplementary conditions such as bill or double confirmation are met; if any source lacks a corresponding record, or if a corresponding record exists but does not meet the preset consistency conditions, the system marks the expenditure as "inconsistent".

[0120] Secondly, the system identifies inconsistencies. If situations such as "the contract stipulates but there is no system record or bank statement", "the bank statement shows but the corresponding record cannot be found in the contract or system", "the system shows a payment or receipt event but the bank has no corresponding transaction record", "the amount is inconsistent", "the entity name is inconsistent", "the invoice is missing or the invoice amount is inconsistent", or "the double confirmation of receipt is not completed" occur, the system will record the corresponding account as abnormal and add it to the list of abnormal accounts.

[0121] Finally, the system generates reconciliation verification vouchers. For accounts that have been matched and determined to be consistent, the system generates reconciliation verification vouchers, recording a summary of the matching results between the contract source, system source, and bank source within the accounting period. For abnormal accounts, the system records the abnormality type, the contract involved, the amount involved, the responsible party, and the processing status in the voucher, serving as the basis for subsequent automatic disclosure and multi-level supervision. For a given payment period, record:

[0122] Total number of expenditures; Number of abnormal expenditures; Total number of revenue transactions; Number of abnormal income transactions.

[0123] definition: The percentage of abnormal expenditures = the number of abnormal expenditures ÷ the total number of expenditures; Abnormal revenue ratio = Number of abnormal revenue transactions ÷ Total number of revenue transactions.

[0124] The system sets two weight parameters: The expenditure-side weighting is: expenditure weighting; The revenue-side weight is: revenue weight.

[0125] The overall abnormality ratio can then be expressed as: Overall abnormality ratio = Expenditure abnormality ratio × Expenditure weight + Revenue abnormality ratio × Revenue weight.

[0126] To facilitate a more intuitive understanding of risk levels by regulatory authorities, the system further converts the overall anomaly ratio into a risk score out of 100 points, for example: Risk score = 100 - (overall abnormality rate × 100).

[0127] Specifically, when the overall anomaly rate is zero, the risk score is 100 points; the higher the overall anomaly rate, the lower the risk score. Regulators can set several risk level ranges. For example, a risk score above 80 points indicates a low risk; a risk score between 60 and 80 points indicates some risk; and a risk score below 60 points indicates a high risk requiring close monitoring.

[0128] Through the above design, this invention establishes the account period risk scoring on the consistency judgment results of each receipt and payment from three sources, so that the automatic reconciliation results no longer rely solely on manual review, but are generated based on the structured matching and algorithm judgment between the contract source, system source and bank source, thus forming the core technical foundation for the automated governance of public funds in this invention. like Figure 7 As shown, the disclosure link not only discloses contract information but also automatically discloses subsequent income and expenditure. Preferably, at the end of each payment period, the system automatically generates disclosure entries based on the reconciliation results, displaying the amount received, the amount paid, the reconciliation status, and whether there are any anomalies under a specific contract for that payment period. Owners can query by contract, by time, or by fund account.

[0129] Therefore, this invention links "resolution disclosure - contract disclosure - income and expenditure disclosure - abnormal disclosure" into a continuous public chain, enabling the public fund governance status to be presented to owners and regulatory authorities in a sustainable and verifiable manner. This invention designs a unified state machine control model for each link, setting state fields and legal state transition conditions for the main nodes of the link. For example:

[0130] The review process includes the following statuses: draft, under public comment, under voting, resolution passed, resolution not passed, and resolution expired. Contract statuses include: draft, pending signing, signing in progress, effective, and terminated. The payment and collection process status includes: pending review, approved, pending execution, executed, and withdrawn. The reconciliation process status includes: pending reconciliation, reconciliation in progress, reconciliation completed, exception found, and resolved. The status of the public announcement link includes: pending announcement, in progress, and completed.

[0131] The link state machine module stipulates that a transition to the next state and the triggering of subsequent links are only permitted when the current link is in a valid state. For example: If a review node that has not reached the "resolution passed" stage cannot be generated, the corresponding contract node cannot be generated. When the public announcement of the corresponding contract decision has not been completed or there are unresolved objections, the contract link shall not be changed from the "signing" status to the "effective" status, nor shall the final official seal be affixed to the contract text; If an internal payment amount review record of "approved" is not generated, a payment event cannot be generated. If a payment event does not match the bank's outgoing transaction record, the entry must not be marked as "reconcilable". When there are any unprocessed abnormal accounts during the payment period, the multi-level supervision chain must display an early warning prompt on the supervision end.

[0132] Through the state machine control described above, this invention enables the execution of each step in the governance of public funds to be non-skipped and non-reversible, thereby technically restricting violations such as "spending before review" and "having funds but no resolution". This invention generates summary values ​​for key events in each link through an authenticity archiving module and forms a chain-like archiving structure. Its steps include summary value generation and storage, summary chain authenticity verification, and generation of administrative law enforcement auxiliary evidence collection package.

[0133] First, the system calculates summary values ​​for key events such as review nodes, contract nodes, payment events, receipt events, bank transaction records, reconciliation results, public disclosure records, regulatory processing records, and anomaly handling records, according to a predetermined summary calculation method. In each event record, in addition to storing the summary value of the current event, the system also stores the summary value of the previous related event, forming a chain structure of "previous summary value + current summary value". When it is necessary to verify the authenticity of historical records, the system recalculates the summary value of each event in chronological order and compares it with the "previous summary value" saved in the record.

[0134] Taking three consecutive events as an example: The original summary value of the first event is: Summary value one; The original summary value of the second event is: Summary Value Two, and the previous summary value saved in the record is: Summary Value One; The original summary value of the third event is: Summary Value Three, and the previous summary value saved in the record is: Summary Value Two.

[0135] The system re-executes the digest operation, resulting in: New summary value 1 = Perform a summary operation on the content of the first event; New summary value 2 = Perform a summary operation on the content of the second event; New summary value three = Perform a summary operation on the content of the third event.

[0136] Then compare: (a) Whether the previous digest value saved in the second event log is equal to the new digest value; (ii) Whether the previous digest value saved in the third event log is equal to the new digest value 2; (iii) Whether the new abstract value is equal to the original abstract value; (iv) Whether the new abstract value 2 is equal to the original abstract value 2; (v) Whether the new abstract value three is equal to the original abstract value three.

[0137] If any of the above comparisons are not equal, it can be inferred that at least one of the corresponding event contents was modified after archiving. The system will mark the event and its subsequent related events as suspected tampered records and synchronize this information to the regulatory chain and the enforcement chain.

[0138] For the entire link, the system defines a digest chain integrity flag, and its determination logic is as follows: If the previous summary value in all event records is exactly the same as the summary value recalculated from the previous event, then the summary chain integrity flag = complete; Otherwise, the digest chain integrity flag indicates an anomaly exists. When regulatory authorities or administrative law enforcement agencies need to investigate the use of public funds for a real estate project, this invention automatically generates an administrative law enforcement auxiliary evidence collection package. This evidence collection package may include:

[0139] Records of the deliberation process and resolutions on the relevant issues; Corresponding contract text and its modification and signing process; The payment and receipt events involved, internal payment review records, double confirmation records of receipts, and invoice images; Bank transaction records and automatic reconciliation results for the corresponding billing period; The process of identifying and handling abnormal accounts; The above records contain summary chain information and summary chain integrity markers.

[0140] Because all records are controlled by the link state machine and archived with a summary chain, law enforcement agencies can use this technical evidence to determine whether a public fund expenditure or income has complete decision-making basis, contractual basis, payment or receipt vouchers, and genuine bank statements, thereby significantly reducing evidence collection costs and the space for dispute.

Claims

1. A multi-link automated management method for public funds in the real estate industry, characterized in that, Includes the following steps: (1) Review Link Steps: When the owners' meeting or owners' committee initiates contract-related issues, the voting results of the majority of owners or members of the community self-governing organization are collected; in accordance with applicable laws and regulations and community deliberation rules, the effective conditions such as the number of meeting participants, the proportion of exclusive area, the voting method, and the publicity period are verified. When the meeting resolution meets the legal effective conditions, the meeting resolution is used as the trigger condition to generate the contract link node. (2) Contract Link Steps: Automatically generate contracts or supplementary agreements based on the contract link nodes, and record the contract text, contract amount, payment or collection plan and list of allowed payment recipients, so that the contract data is stored in a structured manner in the system; (3) Payment or collection chain steps under the contract: When a payment or collection actually occurs in the real estate public fund special account or related supervision special account, a corresponding payment or collection event is recorded. The payment or collection event shall at least include the amount, payment or collection time, payment or collection object, account information and initiator information. (4) External financial account data acquisition steps: The system automatically queries the bank transaction records and receipts of the target account through the external financial account data interface, and writes the bank transaction records and receipts as external authenticity data sources into the system; (5) Automatic reconciliation steps: Based on the contract amount, payment or collection plan, payment or collection object, time characteristics, etc., the bank statement is automatically matched with the allowed payment and collection data and payment or collection events stipulated in the contract; The account status is generated based on the comprehensive matching results of transaction attributes such as the recipient, amount characteristics, and time window; when the matching score does not reach the system-set threshold, the account is recorded as an abnormal account. (6) Automatic disclosure steps: Based on the automatic reconciliation results, financial disclosure content is automatically generated within the statutory disclosure period and displayed to all owners or competent authorities. The financial disclosure content includes at least contract information, payment or receipt event information, bank statement summary information and reconciliation results related to real estate public funds. (7) Multi-level supervision steps: Provide housing and urban-rural development authorities, sub-district offices, community residents' committees and other grassroots management units with contract, payment or collection, reconciliation and public disclosure data within different scopes of authority, so that regulatory bodies at all levels can conduct online supervision and risk identification based on the data; (8) Abnormal account handling steps: The system will notify at least one authorized supervisory body of the abnormal account for collaborative tracking and correction, and will re-trigger the automatic reconciliation step and automatic disclosure step after the correction is completed.

2. A multi-link automated management system for public funds in the real estate industry, characterized in that, This includes: a review process module, a contract process module, a payment process module, an external financial account data interface module, an automatic reconciliation module, an automatic disclosure module, a multi-level supervision module, an abnormal account collaborative processing module, and an administrative law enforcement support module; in: (1) The review link module is used to collect voting results when the owners' meeting or owners' committee initiates the review of contract issues, and to verify the legal conditions for effectiveness such as the number of attendees, the proportion of exclusive area, and the publicity period. When the meeting resolution meets the legal conditions for effectiveness, a contract link node is generated. (2) The contract link module is used to generate a contract or additional agreement based on the contract link node, and record the contract amount, payment or collection plan and list of allowed payment and collection objects; (3) The payment link module is used to generate payment or receipt event records when a payment or receipt actually occurs in the real estate public fund special account or related regulatory special account; (4) The external financial account data interface module is used to obtain the actual receipt and payment flow and return slip data generated by the bank account and introduce them into the system as an external authenticity data source; (5) The automatic reconciliation module is used to build a consistent reconciliation model based on contract data, payment or receipt event data and bank transaction data. It automatically matches the above three sources of data according to algorithms such as amount matching, time window matching, payment and receipt object matching and rule scoring, so as to identify normal accounts and abnormal accounts. (6) The automatic disclosure module is used to automatically generate financial disclosure content based on the automatic reconciliation results and display it to the owner or regulatory body within the statutory disclosure period; (7) The multi-level supervision module is used to display contract link, payment link, reconciliation results and abnormal accounts and other link data to the housing and urban-rural development authorities, street offices, community neighborhood committees and other grassroots management units according to their permissions; (8) The abnormal account collaborative processing module is used to record the reasons for abnormal accounts, rectification measures and rectification results, and to re-trigger the automatic reconciliation and automatic disclosure links after the rectification is completed; (9) The administrative law enforcement auxiliary module is used to automatically generate administrative law enforcement evidence collection packages based on the data of the above-mentioned links, and provide structured data interfaces to administrative law enforcement departments to support the handling of illegal acts and the writing back of law enforcement records.

3. The method according to claim 1, characterized in that, The automatic reconciliation step includes merging and matching multiple bank statements within a preset time window to adapt to installment payment, multi-payment, or cross-day settlement scenarios, thereby improving the matching success rate.

4. The method according to claim 1, characterized in that, The automatic disclosure step automatically triggers the generation of disclosure content based on the status changes of the link nodes. The disclosure content includes at least: disclosure of review decisions, disclosure of contract signing status, disclosure of payment or receipt events, and disclosure of reconciliation results.

5. The method according to claim 1, characterized in that, The abnormal accounts include abnormal situations identified based on the matching results of transaction attribute feature vectors. The abnormal situations include at least the following: the recipients of the bank account are not listed in the allowed recipient list of the contract record, or the total amount of payments or receipts of the bank account deviates from the threshold range agreed in the contract.

6. The system according to claim 2, characterized in that, The external financial account data interface module supports at least one data synchronization mode, including any one or any combination of timed synchronization mode, event-triggered synchronization mode, or real-time synchronization mode.

7. The method according to claim 1, characterized in that, After the meeting resolution is legally passed and a signed contract node is formed, the triggering order between the contract link, the payment or collection link under the contract, the external financial account data acquisition step, the automatic reconciliation step, and the automatic disclosure step can be a preset order or an order automatically determined by the system based on the status of the link node.

8. The method according to claim 1, characterized in that, The contract data, payment or receipt data, and external financial transaction data are stored and managed in a structured manner using a unified data model to achieve automatic data association and matching between different links.

9. The method according to claim 1, characterized in that, The correction process for abnormal accounts includes: supplementing, correcting, or adding explanations to at least one of the contract records, payment or receipt records, or external financial transaction records, and automatically re-triggering the automatic reconciliation step and the automatic disclosure step after correction.

10. The system according to claim 2, characterized in that, The external financial account data interface module is used to connect to the account data interfaces provided by banks, payment institutions, clearing institutions or other financial service platforms with account accounting functions.

11. The method according to claim 1, characterized in that, The triggering methods for the contract link include, but are not limited to, resolutions made by the owners' assembly in accordance with the law, resolutions made by the owners' committee or temporary management committee in accordance with the law, import of regulatory department filings, import of owners' assembly resolutions, import of contract template approval records, or other legal triggering conditions within the system.

12. The method according to claim 1, characterized in that, The automatic public disclosure steps include: automatically generating public disclosure content and publishing it directly in the system, or automatically publishing it after manual confirmation, or automatically associating the file with the corresponding link node when the file is uploaded manually, so that the public disclosure mechanism is not limited by manual or automatic methods.

13. The method according to claim 1, characterized in that, The automatic reconciliation process can be triggered by any one or any combination of the following: automatic system triggering, user command triggering, scheduled task triggering, or external event triggering.

14. The method according to claim 1, characterized in that, The automatic comparison algorithm includes rule matching, amount threshold matching, feature vector matching, machine learning model matching, or any combination thereof, in order to avoid circumventing the protection scope of this invention by using different algorithm forms.

15. The system according to claim 2, characterized in that, The external financial data sources include bank statements, transaction records, electronic account statements, financial data service interfaces, or manually uploaded financial voucher files.

16. The method according to claim 1, characterized in that, The execution order of the links does not affect the implementation effect of the present invention. The triggering relationship between the links can be sequential execution, parallel execution, or asynchronous execution, so as to prevent the present invention from being circumvented by changing the execution order of the links.

17. The system according to claim 2, characterized in that, The multi-level supervision module supports any structural form of single-level supervision, multi-level supervision, cross-departmental supervision, or cross-platform supervision, so as to ensure that different supervision structures are all included in the protection scope of this invention.

18. The method according to claim 1, characterized in that, The system automatically generates administrative law enforcement evidence packages based on link data. These packages include: meeting resolutions, contract records, payment or receipt records, bank transaction records, automatic reconciliation results, and explanations of abnormal accounts. The system also provides structured data to administrative law enforcement departments for handling illegal activities.

19. The system according to claim 2, characterized in that, The administrative law enforcement auxiliary module is used to generate the administrative law enforcement evidence collection package and provide a standardized interface to the administrative law enforcement unit to support the identification of the responsible party for the violation, the preservation of evidence, and the writing back of the processing records.

Images