CN112801792B - Information checking method, device, equipment and storage medium based on SaaS platform - Google Patents
Information checking method, device, equipment and storage medium based on SaaS platform Download PDFInfo
- Publication number
- CN112801792B CN112801792B CN202110126766.4A CN202110126766A CN112801792B CN 112801792 B CN112801792 B CN 112801792B CN 202110126766 A CN202110126766 A CN 202110126766A CN 112801792 B CN112801792 B CN 112801792B
- Authority
- CN
- China
- Prior art keywords
- account
- merchant
- checking
- data
- checked
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q40/00—Finance; Insurance; Tax strategies; Processing of corporate or income taxes
- G06Q40/04—Trading; Exchange, e.g. stocks, commodities, derivatives or currency exchange
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q40/00—Finance; Insurance; Tax strategies; Processing of corporate or income taxes
- G06Q40/12—Accounting
- G06Q40/125—Finance or payroll
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
- Y02D10/00—Energy efficient computing, e.g. low power processors, power management or thermal management
Landscapes
- Business, Economics & Management (AREA)
- Accounting & Taxation (AREA)
- Finance (AREA)
- Engineering & Computer Science (AREA)
- Development Economics (AREA)
- Economics (AREA)
- Marketing (AREA)
- Strategic Management (AREA)
- Technology Law (AREA)
- Physics & Mathematics (AREA)
- General Business, Economics & Management (AREA)
- General Physics & Mathematics (AREA)
- Theoretical Computer Science (AREA)
- Financial Or Insurance-Related Operations Such As Payment And Settlement (AREA)
Abstract
The application discloses an information checking method, device, equipment and storage medium based on a software as a service (SaaS) platform, comprising the following steps: acquiring rules called by each account-checking merchant in the SaaS platform to obtain target rules which represent account checking requirements of the account-checking merchants corresponding to the account-checking merchants; and automatically checking account information of each merchant to be checked in the SaaS platform through a checking process established based on a rule engine frame to obtain a checking result corresponding to the target rule of each merchant to be checked. On the basis of obtaining a target rule representing account checking requirements of merchants, the application provides a general and personalized automatic aggregation account checking service for merchants without self-built account checking systems or with low expansibility and high cost defects in the self-built account checking systems in the SaaS platform by using an account checking flow constructed based on a rule engine framework, and realizes quick and efficient account checking.
Description
Technical Field
The invention relates to the technical field of computers, in particular to an information checking method, device, equipment and storage medium based on a software as a service (SaaS) platform.
Background
Enterprises, as the most basic and active special group in the economic society of China, are widely concerned and paid high attention by parties, governments and social boundaries in recent years, and with continuous development of production and operation and continuous enrichment of business scenes, the business volume of the enterprises is exponentially increased, and the business complexity is gradually improved. In the face of massive transaction data, on one hand, the traditional manual accounting efficiency is extremely low, and the requirements of increasingly violent production and operation activities cannot be met. On the other hand, because the technical capability and the capital capability of small and medium-sized enterprises are limited, the self-built reconciliation software cannot be popularized to each enterprise, and the self-built reconciliation software also has a series of problems of poor maintainability, high access cost, low expansibility, throughput, low real-time performance and the like, thereby bringing great troubles to the reconciliation work of the enterprises with rapidly increased business.
For a large SaaS software as a service provider, different payment capabilities are often required to be provided for diversified account checking services which are safe and stable for enterprises, and transactions are mostly distributed in a plurality of third party payment channels, which directly results in daily and joint increase of order volume and gradual increase of business complexity, thereby providing higher requirements for account checking. The method is oriented to mass orders under multiple payment channels and increasingly complex merchant account checking requirements, ensures account checking efficiency and reduces access cost, and becomes a new mission for enterprises. The traditional software account checking can not meet the increasing demand of orders, and the support of a novel SaaS platform automatic account checking method and system is urgently needed.
Disclosure of Invention
In view of this, an object of the present invention is to provide an information checking method, apparatus, device and storage medium based on a SaaS platform, which can provide a general and personalized automatic aggregation reconciliation service for merchants without a self-established reconciliation system or with low expansibility and high cost in the self-established reconciliation system in the SaaS platform, thereby achieving fast and efficient reconciliation. The specific scheme is as follows:
a first aspect of the present application provides an information checking method based on a SaaS platform, including:
acquiring rules called by each merchant to be checked in the SaaS platform to obtain target rules corresponding to each merchant to be checked and representing the checking requirements of the merchant to be checked;
and automatically checking account information of each merchant to be checked through a checking process constructed based on a rule engine frame to obtain a checking result corresponding to the target rule of each merchant to be checked.
Optionally, the obtaining a rule called by each merchant to be checked in the SaaS platform to obtain a target rule corresponding to each merchant to be checked and representing the checking requirement of the merchant to be checked includes:
acquiring a custom rule obtained by correspondingly configuring the called rule by each account merchant to be checked in the SaaS platform through a visual graph interface;
and determining the custom rule as a target rule corresponding to each account checking merchant and representing the account checking requirement of the account checking merchant.
Optionally, the automatically checking account information of each merchant to be checked through a checking process established based on a rule engine framework to obtain a checking result corresponding to the target rule of each merchant to be checked, including:
and acquiring local end target account data and opposite end target account data of each to-be-checked merchant based on a checking flow established by a rule engine frame, and checking the local end target account data and the opposite end target account data of each to-be-checked merchant one by one to obtain a checking result corresponding to the target rule of each to-be-checked merchant.
Optionally, the respectively obtaining the home terminal target account data and the opposite terminal target account data of each merchant to be reconciled includes:
extracting account information of each account-checking merchant transacting through the SaaS platform from a database of the SaaS platform to obtain home-end target account data of each account-checking merchant;
and downloading the original account data of the opposite terminal through a preset channel, and cleaning the original account data of the opposite terminal to obtain the target account data of the opposite terminal of each merchant to be checked.
Optionally, the cleaning the opposite-end original account data to obtain the opposite-end target account data of each account-checking merchant includes:
screening out account data transacted through the SaaS platform according to the order number in the original account data of the opposite terminal to obtain alternative account data of the opposite terminal;
and determining account data corresponding to the to-be-checked merchant from the opposite-end alternative account data according to the merchant number of the to-be-checked merchant respectively so as to obtain opposite-end target account data of the to-be-checked merchant.
Optionally, the determining, from the alternative account data of the opposite end, account data corresponding to each account merchant to be checked according to the merchant number of each account merchant to be checked to obtain target account data of the opposite end of each account merchant to be checked includes:
determining account data corresponding to each account merchant to be checked from the alternative account data of the opposite terminal according to the merchant number of each account merchant to be checked;
extracting a target field in the account data corresponding to each account merchant to be checked, and determining the target field in the account data corresponding to each account merchant to be checked as the target account data of the opposite end of each account merchant to be checked.
Optionally, the checking, by one, the home-end target account data and the opposite-end target account data of each to-be-checked merchant respectively to obtain a checking result corresponding to the target rule of each to-be-checked merchant includes:
starting a preset number of account data checking threads;
and checking the local end target account data and the opposite end target account data of each account-checking merchant one by utilizing the preset number of account data checking threads to obtain account-checking results corresponding to the target rules of each account-checking merchant.
Optionally, the checking, by using the preset number of account data checking threads, the home-end target account data and the opposite-end target account data of each to-be-checked merchant one by one to obtain a checking result corresponding to the target rule of each to-be-checked merchant, including:
checking the local terminal target account data and the opposite terminal target account data of each to-be-checked merchant one by utilizing the preset number of account data checking threads;
storing data successfully matched with the local terminal target account data and the opposite terminal target account data in a result pool, storing daily account data in a temporary storage pool, and storing other account data in an error pool;
and obtaining a reconciliation result corresponding to the target rule of each merchant to be reconciled according to the data in the result pool, the temporary storage pool and the error pool.
Optionally, after the temporary storage of the daily accounting data in the temporary storage pool, the method further includes:
reading the daily accounting data in the temporary storage pool, judging whether the daily accounting data exceeds a preset period, if so, marking the daily accounting data as opposite-end short account data, and moving the daily accounting data into the error pool.
Optionally, after the account information of each merchant to be checked is automatically checked through the account checking process established based on the rule engine framework to obtain an account checking result corresponding to the target rule of each merchant to be checked, the method further includes:
and if the account checking result contains abnormal account data, alarming the merchant to be checked corresponding to the abnormal account data in a preset alarming mode so as to be convenient for the merchant to be checked to manually process the abnormal account data after receiving alarming information.
Optionally, the alarming the account number to be checked corresponding to the abnormal account data by a preset alarming mode, so that after the account number to be checked receives the alarming information and then performs manual processing on the abnormal account data, the method further includes:
and generating a service statement and uploading the service statement to the COS network disk.
A second aspect of the present application provides an information checking apparatus based on a SaaS platform, including:
the configuration module is used for acquiring rules called by each merchant to be checked in the SaaS platform so as to obtain target rules which are corresponding to each merchant to be checked and represent the checking requirements of the merchant to be checked;
and the reconciliation module is used for automatically checking the account information of each merchant to be reconciled through a reconciliation flow established based on the rule engine framework so as to obtain a reconciliation result corresponding to the target rule of each merchant to be reconciled.
A third aspect of the application provides an electronic device comprising a processor and a memory; the memory is used for storing a computer program, and the computer program is loaded and executed by the processor to implement the information checking method based on the SaaS platform.
A fourth aspect of the present application provides a computer-readable storage medium, where computer-executable instructions are stored in the computer-readable storage medium, and when the computer-executable instructions are loaded and executed by a processor, the information checking method based on the SaaS platform is implemented.
In the method, rules called by each account checking merchant to be checked in the SaaS platform are firstly acquired so as to obtain target rules which represent account checking requirements of the account checking merchants to be checked and correspond to the account checking merchants to be checked, and then account information of the account checking merchants to be checked and correspond to the target rules of the account checking merchants to be checked and correspond to the account checking results through an account checking flow established based on a rule engine frame. On the basis of obtaining a target rule representing account checking requirements of merchants, the application provides a general and personalized automatic aggregation account checking service for merchants without self-built account checking systems or with low expansibility and high cost defects in the self-built account checking systems in the SaaS platform by using an account checking flow constructed based on a rule engine framework, and realizes quick and efficient account checking.
Drawings
In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below, it is obvious that the drawings in the following description are only embodiments of the present invention, and for those skilled in the art, other drawings can be obtained according to the provided drawings without creative efforts.
Fig. 1 is a flowchart of an information checking method based on a SaaS platform according to the present application;
FIG. 2 is a schematic diagram of a reconciliation rule engine structure provided by the present application;
fig. 3 is a schematic diagram of an information checking method based on a SaaS platform according to the present application;
fig. 4 is a flowchart of a specific information checking method based on a SaaS platform according to the present application;
fig. 5 is a schematic diagram of a specific information checking method based on a SaaS platform according to the present application;
fig. 6 is a schematic diagram of a process for acquiring original account data of an opposite end according to the present application;
fig. 7 is a schematic diagram of a process for acquiring peer target account data according to the present application;
FIG. 8 is a schematic diagram of a reconciliation batch construction method provided by the present application;
FIG. 9 is a diagram illustrating a specific process for processing scratch pad pool data according to the present application;
fig. 10 is a schematic structural diagram of an information checking apparatus based on a SaaS platform according to the present application;
fig. 11 is a structural diagram of an information checking electronic device based on a SaaS platform according to the present application.
Detailed Description
The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
At present, the efficiency of account checking work completed by a manual account keeping mode is low, the increasing business requirements of enterprises cannot be met, and self-built account checking software has a series of problems of low automation degree, good and uneven quality, single function, poor expansibility, high access threshold and the like, and is not friendly to medium and small enterprises. The existing account checking method cannot provide safe and stable diversified account checking services for merchants of the SaaS platform, and the automatic account checking method and system of the novel SaaS platform are urgently needed to be supported. In order to overcome the technical problems, the information checking scheme based on the SaaS platform is provided, and the method and the system can provide universality and personalized automatic aggregation reconciliation service for merchants without self-built reconciliation systems or with the defects of low expansibility and high cost in the SaaS platform, so that the rapid and efficient reconciliation is realized.
Fig. 1 is a flowchart of an information checking method based on a SaaS platform according to an embodiment of the present disclosure. Referring to fig. 1, the information checking method based on the SaaS platform includes:
s11: and acquiring rules called by each merchant to be checked in the SaaS platform to obtain target rules corresponding to each merchant to be checked and representing the checking requirements of the merchant to be checked.
In this embodiment, first, a rule called by each account checking merchant in the SaaS platform is obtained, so as to obtain a target rule corresponding to each account checking merchant and representing the account checking requirement of the account checking merchant. Before the above steps are performed, an account checking rule engine required for account checking in this embodiment may be constructed based on a rule engine framework, which may be an open source rule engine framework or a business rule engine framework. The reconciliation rule engine can adapt to SaaS software requirements, service requirement separation and technology realization are separated as much as possible by adopting a configuration mode rather than a program coding mode, codes of an operation interface, codes of service logic and codes of a database layer corresponding to rules called by each account checking merchant in the SaaS platform are automatically generated through the configuration mode, and the realization mode of reconciliation service logic change is effectively solved.
In this embodiment, the reconciliation rule engine is abstracted into roles such as a caller, an operator, an engine provider, a service engine, a scene, a rule, a general rule, and the like, and can be specifically abstracted into a structure shown in fig. 2. The caller dynamically inputs, modifies and deletes the data through graphical input, acquires the required scenes, rules and general rules from the database, and can take effect without restarting the system, namely the method is suitable for plug-in and hot update implementation modes. The scene is the set of the rules, and can be understood as a rule package. In the face of complex service scenes, variable comparison rules, various data sources and interface protocols, an access party only needs to pay attention to the setting of the rules without paying attention to a specific implementation process, so that the access cost of the reconciliation system is greatly reduced. It should be noted that, in this embodiment, the rule that is obtained and called by each account checking merchant in the SaaS platform may be an original rule package provided by the account checking rule engine itself, and directly determine the original rule package as the target rule, or may be the target rule that represents the account checking requirement of the account checking merchant and obtained after the merchant performs corresponding configuration through graphical input according to the own requirement.
S12: and automatically checking account information of each account-waiting merchant through an account checking flow constructed based on a rule engine frame to obtain an account checking result corresponding to the target rule of each account-waiting merchant.
In this embodiment, account information of each account-waiting merchant is automatically checked through an account checking process established based on a rule engine framework, so as to obtain an account checking result corresponding to the target rule of each account-waiting merchant. The reconciliation flow constructed based on the rule engine framework is the reconciliation flow of the reconciliation rule engine in step S11, in the embodiment, the reconciliation process of each merchant to be reconciled in the SaaS platform based on the reconciliation flow of the reconciliation rule engine does not need to write specific codes for specific channels and specific merchants, and a caller completes automatic reconciliation through the collection, calculation, storage, report generation, uploading and other flows provided by the reconciliation rule engine provider, as shown in fig. 3. The embodiment introduces the result pool on the basis of the temporary storage pool and the error pool in the general account checking process, ensures the correctness of information flow and the accuracy of fund flow, and can also smoothen account checking which is not smooth due to the system environment through manual participation.
As can be seen, in the embodiment of the application, firstly, the rule called by each account-checking merchant in the SaaS platform is obtained to obtain the target rule corresponding to each account-checking merchant and representing the account-checking requirement of each account-checking merchant, and then, the account information of each account-checking merchant is automatically checked through the account-checking process established based on the rule engine framework, so as to obtain the account-checking result corresponding to the target rule of each account-checking merchant. On the basis of obtaining a target rule representing account checking requirements of merchants, the embodiment of the application provides a general and personalized automatic aggregation account checking service for merchants without self-built account checking systems or with low expansibility and high cost defects in the self-built account checking systems in the SaaS platform by using the account checking process built based on the rule engine framework, so that quick and efficient account checking is realized.
Fig. 4 is a flowchart of a specific information checking method based on a SaaS platform according to an embodiment of the present application, and fig. 5 is a schematic diagram of a specific information checking method based on a SaaS platform according to the present application. Referring to fig. 4 and 5, the information checking method based on the SaaS platform includes:
s21: the method comprises the steps of obtaining a custom rule obtained after each account-checking merchant in the SaaS platform carries out corresponding configuration on a called rule through a visual graph interface, and determining the custom rule as a target rule which is corresponding to each account-checking merchant and represents account checking requirements of the account-checking merchant.
In this embodiment, first, a customized rule obtained by configuring a called rule by each account-checking merchant in the SaaS platform through a visual graphical interface is obtained, and then the customized rule is determined as a target rule corresponding to each account-checking merchant and representing the account-checking requirement of the account-checking merchant. Therefore, the steps may be preceded by loading the caller, engine provider, scenario, rules and data model, and the rules may be invoked upon loading the rules, corresponding to the engine loading shown in fig. 5. The custom rule is obtained by dynamically inputting, modifying, deleting and the like the called original rule through graphical input, and meets the personalized and diversified account checking requirements of different merchants through plug-in design on the basis of providing the general account checking rule. In this embodiment, the target rule may be in various forms of presentation, such as checking bills of different payment channels separately or checking bills in a specified checking period.
S22: and extracting account information of each account-checking merchant transacting through the SaaS platform from a database of the SaaS platform based on an account-checking flow established by a rule engine framework so as to obtain home-end target account data of each account-checking merchant.
In this embodiment, based on an account checking process established by a rule engine framework, account information of each account checking merchant transacting through the SaaS platform is extracted from a database of the SaaS platform, so as to obtain home-end target account data of each account checking merchant. The acquisition of the home terminal target account data is relatively simple, and the account information transacted through the SaaS platform can be directly extracted from the database of the SaaS platform. However, it should be noted that, when the SaaS platform stores local account information, and under the condition that the data storage formats are not uniformly limited, for convenience of checking, the format of the local target account data may be correspondingly transformed according to the format of the opposite-end target account data or the attribute field of the local target account data may be correspondingly extracted according to the attribute field of the opposite-end target account data.
S23: and downloading the original account data of the opposite terminal through a preset channel based on an account checking flow established by a rule engine frame, and clearing out the account data transacted through the SaaS platform according to an order number in the original account data of the opposite terminal so as to obtain alternative account data of the opposite terminal.
In this embodiment, the account data of the opposite end is the account data provided by the payment mechanism, and obtaining the account data of the opposite end may be colloquially referred to as statement download, and the payment mechanism includes but is not limited to a bank, a payer, a WeChat, and the like. Firstly, downloading opposite-end original account data through preset channels based on a reconciliation flow established by a rule engine framework, wherein the preset channels comprise three types: the payment mechanism pushes the statement of account to a designated HTTP/SFTP/FTP at regular time, and the rule engine needs to pull the statement of account from the SFTP/FTP for a plurality of times at regular time; or calling an interface provided by the payment mechanism for downloading the reconciliation file, wherein the mode needs the payment mechanism to provide the interface for downloading the reconciliation file, and the rule engine calls downloading regularly; or the reconciliation file is downloaded in the website of the payment mechanism manually, which is the mode which is not friendly and wastes a great deal of human resources.
Because the format of the reconciliation file obtained from different channels is not uniform, for example, the statements of some channels can be encrypted or provided with a zip packaging format, a zip tool class or an encryption/decryption tool class needs to be additionally used for processing, and the processing process is tedious, so that after the reconciliation file is obtained, files in different formats of different channels can be automatically resolved into a uniform data type capable of being reconciled by using a factory design mode, wherein the resolved file type generally comprises: json, text, cvs, excel files, and the like. In this embodiment, the reconciliation file provided by the payment mechanism is downloaded into a database according to a protocol (HTTP or SFTP or FTP) preset by the target rule, and after the file is analyzed into a uniform data type, the integrity of the file is verified, the verification is correct, and the downloading process is ended, and if abnormal conditions such as file damage and file incompleteness occur, the downloading process is repeated, as shown in fig. 6.
That is, after the opposite-end original account data in this embodiment is obtained, because the opposite-end original account data includes the account data of the order of the transaction platform except for the SaaS platform, the account data transacted through the SaaS platform needs to be screened out according to the order number in the opposite-end original account data to obtain the opposite-end alternative account data, it is understood that a certain corresponding relationship exists between the order number and the transaction platform, for example, a transaction order with an order number beginning with 01 belonging to the SaaS platform, and an order corresponding to such an order number is determined as the opposite-end alternative account data in this embodiment, as shown in fig. 7.
S24: and determining account data corresponding to each account checking merchant from the opposite-end alternative account data according to the merchant number of each account checking merchant, extracting a target field in the account data corresponding to each account checking merchant, and determining the target field in the account data corresponding to each account checking merchant as the opposite-end target account data of each account checking merchant.
In this embodiment, the account data of the opposite end includes account data of a plurality of different merchants in the SaaS platform, from which the account data of the merchant to be reconciled needs to be screened out. Firstly, determining account data corresponding to each account to be checked from the opposite-end alternative account data according to the merchant number of each account to be checked, wherein a corresponding relationship also exists between the merchant number and the merchant as described above. Then, extracting a target field in the account data corresponding to each account-checking merchant, and determining the target field in the account data corresponding to each account-checking merchant as the target account data of the opposite end of each account-checking merchant, as shown in fig. 7. Wherein the target field includes, but is not limited to, an order number, a merchant number, a transaction time, a transaction amount, etc. In addition, in order to increase a certain system fault tolerance and avoid the need of repeatedly checking and reconciling the orders of the batch, the above steps are repeatedly executed to obtain the target account data of the opposite end.
S25: and opening a preset number of account data checking threads, and checking the home terminal target account data and the opposite terminal target account data of each to-be-checked merchant one by using the preset number of account data checking threads.
In this embodiment, a preset number of account data checking threads are started, and the local end target account data and the opposite end target account data of each to-be-checked merchant are checked one by using the preset number of account data checking threads. Considering that the account checking environment is complex, a bilateral account checking mode is adopted in the program, the account checking speed is improved by using multiple threads, a memory queue and a temporary storage pool, transaction data are equally divided into multiple parts, the multiple parts of transaction data are checked by multiple servers, the accounts are checked on each server by using the multiple threads at the same time, and compared with the single-thread account checking of the transaction data by a single server, the efficiency is improved by multiple times. In addition, the account data of different payment institutions can be divided into different batches to be checked simultaneously, for example, the account data of a payment institution which is WeChat and the account data of a payment institution which is a Payment treasure are divided into two batches, and the two batches of account data are checked simultaneously by using a plurality of threads, so that the processing modes of multiple batches and multiple threads are adopted, and the overall processing time is reduced. It should be noted that the batch creation modes are various, the above-mentioned batching the account data of different payment mechanisms is one of them, and the merchant to be checked can also be batched according to the checking period, for example, a merchant with a checking period of T is divided into one batch, a merchant with a checking period of T +1 is divided into another batch, and so on, as shown in fig. 8. The bilateral reconciliation is to be respectively reconciled with the payment mechanism data one by one with the platform data as the standard and reconciled with the platform data one by one with the payment mechanism data as the standard, and the main attribute of the reconciliation is the amount and the state in the account data corresponding to different orders, which corresponds to the reconciliation logic processing part in fig. 5.
S26: storing data successfully matched with the local terminal target account data and the opposite terminal target account data in a result pool, storing daily account switching data in a temporary storage pool, storing other account data in an error pool, reading the daily account switching data in the temporary storage pool, judging whether the daily account switching data exceeds a preset period, if so, marking the daily account switching data as opposite terminal short account data, and moving the daily account switching data into the error pool.
In this example, three types of data are generated during the blending process: and (4) checking error-free data, long and short money data caused by daily cutting problems and long and short money data caused by inconsistent money amount or state. And directly storing the data which is checked to be correct in the result pool, putting the data which is caused by daily cutting into the temporary storage pool, continuing checking in a subsequent reconciliation period, storing other account data in an error pool, and waiting for subsequent manual processing. It should be noted that, in order to not occupy the error pool resource, the data that is not successful at the opposite end or at the home end or the data with inconsistent money amount is put into the error pool, and the data that is successful at the opposite end or unsuccessful at the home end, which is caused by the fact that the asynchronous notification of the channel party is not received or the completion of the repair order is not successful, only needs to turn the state of the home end to be successful with the payment mechanism as the standard.
Further, for each account checking period, the daily accounting data in the temporary storage pool needs to be read, whether the daily accounting data exceeds a preset period is judged, if yes, the daily accounting data is marked as opposite-end short account data, and the daily accounting data is moved into the error pool. The preset period is a storage time of the daily accounting data in an error pool, when the daily accounting data is in the preset period, the daily accounting data needs to be matched with the opposite-end target accounting data or the local-end target accounting data, if the corresponding accounting data is matched, the daily accounting data is moved into the result pool, and if the corresponding accounting data is not matched, the matching operation is continued in a next accounting period until the preset period is ended or the matching is successful, which is specifically shown in fig. 9.
And for data in the error pool, manually carrying out error processing, and leveling accounts through manual account hanging, account posting, account adjusting and the like. The multi-account data is subjected to account checking processing, wherein the multi-account is generally caused by that asynchronous notification is not received, and order supplementing processing or double payment with an order is preferably adopted. The short account data is generally coordinated and processed with a payment mechanism through a signature anti-repudiation mechanism, and after coordination and consistency, the account is leveled through manually adding bills. For the problem of inconsistent amount, the transaction amount, earnings and accounts payable need to be determined and really happened, and the account is adjusted after manual processing.
S27: and obtaining a reconciliation result corresponding to the target rule of each merchant to be reconciled according to the data in the result pool, the temporary storage pool and the error pool.
In this embodiment, a reconciliation result corresponding to the target rule of each reconciliation merchant is obtained according to the data in the result pool, the temporary storage pool, and the error pool, and if the reconciliation result is abnormal, the reconciliation merchant corresponding to the abnormal account data is alerted in a preset alert mode, so that the reconciliation merchant receives alert information and then manually processes the abnormal account data, and the alert mode can be sending an alert mail or a short message to the reconciliation merchant. In addition, a service statement bill can be generated according to the final statement account result, and the service statement bill is uploaded to the COS network disk, so that compared with a statement bill which is manually generated and stored on a personal computer of a financial staff, the data is not easy to lose in the unified storage mode in the embodiment, and the statement bill can be checked by multiple people on line.
Obviously, in the embodiment of the application, the target rule representing the account checking requirement of each account checking merchant is obtained by performing custom configuration on the rule, then the local target account data of each account checking merchant is obtained based on the account checking process constructed by the rule engine framework, and the opposite end target account data is obtained through a series of operations such as downloading, analyzing and cleaning. And finally, starting a preset number of account data checking threads, checking the home terminal target account data and the opposite terminal target account data of each account merchant to be checked one by using the preset number of account data checking threads, and circulating the account data by using a result pool, a temporary storage pool and an error pool to obtain an account checking result corresponding to the target rule of each account merchant to be checked. The steps enable the business rule configuration and the business configuration to be visualized, and meanwhile, the distributed service is used for fragmenting the data, so that the throughput of the system is greatly improved, and the account checking efficiency is further improved.
Referring to fig. 10, an embodiment of the present application further discloses an information checking apparatus based on a SaaS platform, which includes:
the configuration module 11 is configured to acquire a rule called by each account-waiting merchant in the SaaS platform, so as to obtain a target rule representing the account-checking requirement of each account-waiting merchant corresponding to each account-waiting merchant;
the reconciliation module 12 is configured to perform automatic reconciliation on the account information of each merchant to be reconciled through a reconciliation flow established based on the rule engine framework, so as to obtain a reconciliation result corresponding to the target rule of each merchant to be reconciled.
As can be seen, in the embodiment of the application, firstly, the rule called by each account-checking merchant in the SaaS platform is obtained to obtain the target rule corresponding to each account-checking merchant and representing the account-checking requirement of each account-checking merchant, and then, the account information of each account-checking merchant is automatically checked through the account-checking process established based on the rule engine framework, so as to obtain the account-checking result corresponding to the target rule of each account-checking merchant. On the basis of obtaining a target rule representing account checking requirements of merchants, the embodiment of the application provides a general and personalized automatic aggregation account checking service for merchants without self-built account checking systems or with low expansibility and high cost defects in the self-built account checking systems in the SaaS platform by using the account checking process built based on the rule engine framework, so that quick and efficient account checking is realized.
In some specific embodiments, the obtaining configuration module 11 specifically includes:
the rule unit is used for acquiring a custom rule obtained after each account merchant to be checked in the SaaS platform performs corresponding configuration on the called rule through a visual graphic interface;
and the determining unit is used for determining the custom rule as a target rule which is corresponding to each account checking merchant and represents the account checking requirement of the account checking merchant.
In some specific embodiments, the reconciliation module 12 specifically includes:
the extracting unit is used for extracting account information of transactions of the merchants to be account checked through the SaaS platform from a database of the SaaS platform so as to obtain home-end target account data of the merchants to be account checked;
the downloading unit is used for downloading the original account data of the opposite terminal through a preset channel;
the screening unit is used for screening out the account data which is transacted through the SaaS platform according to the order number in the original account data of the opposite terminal so as to obtain alternative account data of the opposite terminal;
a determining unit, configured to determine, according to the merchant number of each account-checking merchant, account data corresponding to each account-checking merchant from the opposite-end alternative account data, so as to obtain opposite-end target account data of each account-checking merchant;
the reconciliation unit is used for starting a preset number of account data checking threads and checking the target account data of the home terminal and the target account data of the opposite terminal of each account-checking merchant one by utilizing the preset number of account data checking threads so as to obtain a reconciliation result corresponding to the target rule of each account-checking merchant;
the storage unit is used for storing data successfully matched with the local terminal target account data and the opposite terminal target account data in a result pool, storing daily accounting data in a temporary storage pool, and storing other account data in an error pool;
the reading unit is used for reading the daily accounting data in the temporary storage pool, judging whether the daily accounting data exceeds a preset period, if so, marking the daily accounting data as short account data at the opposite end, and moving the daily accounting data into the error pool;
a result unit, configured to obtain a reconciliation result corresponding to the target rule of each merchant to be reconciled according to data in the result pool, the temporary storage pool, and the error pool;
and the warning unit is used for warning the merchant to be checked corresponding to the abnormal account data in a preset warning mode if the abnormal account data exists in the checking result so as to facilitate the merchant to be checked to manually process the abnormal account data after receiving warning information.
Further, the embodiment of the application also provides electronic equipment. FIG. 11 is a block diagram illustrating an electronic device 20 according to an exemplary embodiment, and nothing in the figure should be taken as a limitation on the scope of use of the present application.
Fig. 11 is a schematic structural diagram of an electronic device 20 according to an embodiment of the present disclosure. The electronic device 20 may specifically include: at least one processor 21, at least one memory 22, a power supply 23, a communication interface 24, an input output interface 25, and a communication bus 26. The memory 22 is configured to store a computer program, and the computer program is loaded and executed by the processor 21 to implement relevant steps in the SaaS platform-based information checking method disclosed in any of the foregoing embodiments. In addition, the electronic device 20 in this embodiment may be specifically a server.
In this embodiment, the power supply 23 is configured to provide a working voltage for each hardware device on the electronic device 20; the communication interface 24 can create a data transmission channel between the electronic device 20 and an external device, and a communication protocol followed by the communication interface is any communication protocol that can be applied to the technical solution of the present application, and is not specifically limited herein; the input/output interface 25 is configured to obtain external input data or output data to the outside, and a specific interface type thereof may be selected according to specific application requirements, which is not specifically limited herein.
In addition, the memory 22 is used as a carrier for resource storage, and may be a read-only memory, a random access memory, a magnetic disk or an optical disk, etc., and the resources stored thereon may include an operating system 221, a computer program 222, and account data 223, etc., and the storage manner may be a transient storage or a permanent storage.
The operating system 221 is used for managing and controlling each hardware device and the computer program 222 on the electronic device 20, so as to realize the operation and processing of the mass account 223 in the memory 22 by the processor 21, which may be Windows Server, netware, unix, linux, or the like. The computer program 222 may further include a computer program that can be used to perform other specific tasks in addition to the computer program that can be used to perform the SaaS platform-based information collation method executed by the electronic device 20 disclosed in any of the foregoing embodiments. Data 223 may include accounting data collected by electronic device 20.
Further, an embodiment of the present application further discloses a storage medium, where a computer program is stored in the storage medium, and when the computer program is loaded and executed by a processor, the steps of the information checking method based on the SaaS platform disclosed in any of the foregoing embodiments are implemented.
In the present specification, the embodiments are described in a progressive manner, and each embodiment focuses on differences from other embodiments, and the same or similar parts between the embodiments are referred to each other. The device disclosed in the embodiment corresponds to the method disclosed in the embodiment, so that the description is simple, and the relevant points can be referred to the description of the method part.
Finally, it should also be noted that, in this document, relational terms such as first and second, and the like are used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. Also, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising a" \8230; "does not exclude the presence of additional like elements in a process, method, article, or apparatus that comprises the element.
The information checking method, device, equipment and storage medium based on the SaaS platform provided by the invention are described in detail above, a specific example is applied in the text to explain the principle and the implementation of the invention, and the description of the above embodiment is only used to help understanding the method and the core idea of the invention; meanwhile, for a person skilled in the art, according to the idea of the present invention, there may be variations in the specific embodiments and the application scope, and in summary, the content of the present specification should not be construed as a limitation to the present invention.
Claims (7)
1. An information checking method based on a software as a service (SaaS) platform is characterized by comprising the following steps of:
acquiring rules called by each merchant to be checked in the SaaS platform to obtain target rules corresponding to each merchant to be checked and representing the checking requirements of the merchant to be checked;
automatically checking account information of each account-waiting merchant through an account checking flow constructed based on a rule engine frame to obtain an account checking result corresponding to the target rule of each account-waiting merchant;
the automatic reconciliation of the account information of each merchant to be reconciled through the reconciliation flow established based on the rule engine framework to obtain a reconciliation result corresponding to the target rule of each merchant to be reconciled comprises the following steps:
acquiring local end target account data and opposite end target account data of each to-be-checked merchant based on a checking flow established by a rule engine frame, and checking the local end target account data and the opposite end target account data of each to-be-checked merchant one by one to obtain a checking result corresponding to the target rule of each to-be-checked merchant;
the acquiring of the home terminal target account data and the opposite terminal target account data of each to-be-reconciled merchant includes:
extracting account information of each account-checking merchant transacting through the SaaS platform from a database of the SaaS platform to obtain home-end target account data of each account-checking merchant;
downloading original account data of an opposite terminal through a preset channel;
screening out account data transacted through the SaaS platform according to the order number in the original account data of the opposite terminal to obtain alternative account data of the opposite terminal;
determining account data corresponding to each account merchant to be checked from the alternative account data of the opposite terminal according to the merchant number of each account merchant to be checked;
extracting a target field in the account data corresponding to each account merchant to be checked, and determining the target field in the account data corresponding to each account merchant to be checked as opposite-end target account data of each account merchant to be checked;
the checking the local terminal target account data and the opposite terminal target account data of each merchant to be checked one by one respectively to obtain a checking result corresponding to the target rule of each merchant to be checked includes:
starting a preset number of account data checking threads;
checking the local terminal target account data and the opposite terminal target account data of each to-be-checked merchant one by utilizing the preset number of account data checking threads;
storing data successfully matched with the local terminal target account data and the opposite terminal target account data in a result pool, storing daily accounting data in a temporary storage pool, and storing other account data in an error pool;
obtaining reconciliation results corresponding to the target rules of the merchants to be reconciled according to the data in the result pool, the temporary storage pool and the error pool;
reading the daily accounting data in the temporary storage pool, judging whether the daily accounting data exceeds a preset period, if so, marking the daily accounting data as opposite-end short account data, and moving the daily accounting data into the error pool.
2. The information checking method based on the SaaS platform according to claim 1, wherein the obtaining of the rule called by each account-waiting merchant in the SaaS platform to obtain the target rule corresponding to each account-waiting merchant and representing the account-checking requirement of the account-waiting merchant comprises:
acquiring a custom rule obtained by correspondingly configuring the called rule by each account merchant to be checked in the SaaS platform through a visual graph interface;
and determining the custom rule as a target rule corresponding to each merchant to be checked and representing the checking requirement of the merchant to be checked.
3. The information checking method based on the SaaS platform according to claim 1 or 2, wherein after the account information of each account-waiting business is automatically checked through a checking flow constructed based on a rule engine framework to obtain a checking result corresponding to the target rule of each account-waiting business, the method further comprises:
and if the account checking result contains abnormal account data, alarming the merchant to be checked corresponding to the abnormal account data in a preset alarming mode so as to facilitate the merchant to be checked to manually process the abnormal account data after receiving alarming information.
4. The information checking method based on the SaaS platform according to claim 3, wherein the alerting the account waiting merchant corresponding to the abnormal account data by a preset alerting manner, so that after the account waiting merchant receives the alerting information and then manually processes the abnormal account data, further comprising:
and generating a service statement and uploading the service statement to the COS network disk.
5. An information checking apparatus based on a SaaS platform, comprising:
the configuration module is used for acquiring rules called by each merchant to be checked in the SaaS platform so as to obtain target rules which are corresponding to each merchant to be checked and represent the checking requirements of the merchant to be checked;
the account checking module is used for automatically checking account information of each account-waiting merchant through an account checking process constructed based on a rule engine framework so as to obtain an account checking result corresponding to the target rule of each account-waiting merchant;
the information checking device based on the SaaS platform is further used for:
acquiring local end target account data and opposite end target account data of each to-be-checked merchant based on a checking flow established by a rule engine frame, and checking the local end target account data and the opposite end target account data of each to-be-checked merchant one by one to obtain a checking result corresponding to the target rule of each to-be-checked merchant;
extracting account information of each account-checking merchant transacting through the SaaS platform from a database of the SaaS platform to obtain home-end target account data of each account-checking merchant;
downloading original account data of the opposite terminal through a preset channel;
screening out account data transacted through the SaaS platform according to the order number in the original account data of the opposite terminal to obtain alternative account data of the opposite terminal;
determining account data corresponding to each merchant to be checked from the alternative account data of the opposite terminal according to the merchant number of each merchant to be checked;
extracting a target field in the account data corresponding to each merchant to be reconciled, and determining the target field in the account data corresponding to each merchant to be reconciled as the opposite-end target account data of each merchant to be reconciled;
starting a preset number of account data checking threads;
performing a batch-by-batch check on the home terminal target account data and the opposite terminal target account data of each to-be-checked merchant by using the preset number of account data check threads;
storing data successfully matched with the local terminal target account data and the opposite terminal target account data in a result pool, storing daily accounting data in a temporary storage pool, and storing other account data in an error pool;
obtaining reconciliation results corresponding to the target rules of the merchants to be reconciled according to the data in the result pool, the temporary storage pool and the error pool;
reading the daily account-cutting data in the temporary storage pool, judging whether the daily account-cutting data exceeds a preset period, if so, marking the daily account-cutting data as opposite-end short account data, and moving the daily account-cutting data into the error pool.
6. An electronic device, comprising a processor and a memory; wherein the memory is used for storing a computer program, which is loaded and executed by the processor to implement the SaaS platform-based information collating method according to any one of claims 1 to 4.
7. A computer-readable storage medium storing computer-executable instructions which, when loaded and executed by a processor, implement the SaaS platform-based information collation method according to any one of claims 1 to 4.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110126766.4A CN112801792B (en) | 2021-01-29 | 2021-01-29 | Information checking method, device, equipment and storage medium based on SaaS platform |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110126766.4A CN112801792B (en) | 2021-01-29 | 2021-01-29 | Information checking method, device, equipment and storage medium based on SaaS platform |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN112801792A CN112801792A (en) | 2021-05-14 |
| CN112801792B true CN112801792B (en) | 2023-04-07 |
Family
ID=75812874
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202110126766.4A Active CN112801792B (en) | 2021-01-29 | 2021-01-29 | Information checking method, device, equipment and storage medium based on SaaS platform |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112801792B (en) |
Families Citing this family (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113591446B (en) * | 2021-06-29 | 2023-11-03 | 四川新网银行股份有限公司 | Configurational account checking file generating device |
| CN113486059A (en) * | 2021-07-23 | 2021-10-08 | 重庆富民银行股份有限公司 | Multi-thread-based account checking method and system |
| CN115379007B (en) * | 2022-10-27 | 2023-04-07 | 云账户技术(天津)有限公司 | Bill verification method, device, equipment and storage medium based on SaaS |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109493201A (en) * | 2018-09-18 | 2019-03-19 | 深圳壹账通智能科技有限公司 | Account checking method, device, computer equipment and storage medium |
| CN111798296A (en) * | 2020-06-15 | 2020-10-20 | 远光软件股份有限公司 | Automatic account checking method, automatic account checking device and computer readable storage medium |
| CN111901404A (en) * | 2020-07-20 | 2020-11-06 | 山东浪潮易云在线科技有限公司 | Financial account checking service implementation method based on SaaS mode |
Family Cites Families (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103164206A (en) * | 2011-12-16 | 2013-06-19 | 上海博腾信息科技有限公司 | Software customization system based on software as a service (SAAS) |
| CN108629592B (en) * | 2018-04-28 | 2023-10-24 | 北京三快在线科技有限公司 | Settlement configuration method and device and electronic equipment |
| CN109816501A (en) * | 2018-12-26 | 2019-05-28 | 天翼电子商务有限公司 | Intelligent reconciliation system, method and server |
| CN110765179A (en) * | 2019-10-18 | 2020-02-07 | 京东数字科技控股有限公司 | Distributed account checking processing method, device, equipment and storage medium |
| CN111402022A (en) * | 2020-03-10 | 2020-07-10 | 北京意锐新创科技有限公司 | Merchant account checking method and device |
-
2021
- 2021-01-29 CN CN202110126766.4A patent/CN112801792B/en active Active
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109493201A (en) * | 2018-09-18 | 2019-03-19 | 深圳壹账通智能科技有限公司 | Account checking method, device, computer equipment and storage medium |
| CN111798296A (en) * | 2020-06-15 | 2020-10-20 | 远光软件股份有限公司 | Automatic account checking method, automatic account checking device and computer readable storage medium |
| CN111901404A (en) * | 2020-07-20 | 2020-11-06 | 山东浪潮易云在线科技有限公司 | Financial account checking service implementation method based on SaaS mode |
Also Published As
| Publication number | Publication date |
|---|---|
| CN112801792A (en) | 2021-05-14 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN112801792B (en) | Information checking method, device, equipment and storage medium based on SaaS platform | |
| US11842354B1 (en) | Risk detection of false customer information | |
| US20190251234A1 (en) | Authentication challenges based on fraud initiation requests | |
| US20200265409A1 (en) | Systems and methods to split bills and requests for payment from debit or credit account | |
| US11416863B2 (en) | System and methods for assessing risk of fraud in an electronic transaction | |
| CN112163946A (en) | Accounting processing method and device based on distributed transaction system | |
| CN113205402A (en) | Account checking method and device, electronic equipment and computer readable medium | |
| US20160086177A1 (en) | Smart Gross Management of Repairs and Exceptions for Payment Processing | |
| CN112184240A (en) | Refund request processing method and device | |
| US20120158583A1 (en) | Automated bank transfers using identifier tokens | |
| US8914308B2 (en) | Method and apparatus for initiating a transaction on a mobile device | |
| CN113056761A (en) | Payment platform management method, device, payment platform and computer storage medium | |
| US10740760B2 (en) | Framework for managing online transactions in internet of things (IoT) | |
| US20220164868A1 (en) | Real-time online transactional processing systems and methods | |
| US10216830B2 (en) | Multicomputer processing of client device request data using centralized event orchestrator and link discovery engine | |
| US20230297995A1 (en) | Allocating payment transaction portions to more than one funding source via a single card | |
| US11934375B2 (en) | System for automatic data transfer acceleration | |
| US20240185216A1 (en) | Systems and methods for communication and negotiation of request for payment over payment networks | |
| US20230046386A1 (en) | Multi-part request for transfers | |
| US20240152886A1 (en) | Systems and methods for funds transfer account aggregator | |
| CN111882294B (en) | Method and device for flow approval | |
| US20220309500A1 (en) | Handling bulk file processing while maintain file level consistency | |
| US20220383278A1 (en) | Systems and methods for configuring resource transfers | |
| US20240039857A1 (en) | Systems and method for improving network traffic | |
| CN113592571A (en) | Bill issuing early warning method, device, equipment and computer readable medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |