Detailed Description
Reference will now be made in detail to exemplary embodiments, examples of which are illustrated in the accompanying drawings. When the following description refers to the accompanying drawings, the same numbers in different drawings refer to the same or similar elements, unless otherwise indicated. The implementations described in the following exemplary examples do not represent all implementations consistent with the present specification. Rather, they are merely examples of apparatus and methods consistent with some aspects of the present description as detailed in the accompanying claims.
The terminology used in the description presented herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the description. As used in this specification and the appended claims, the singular forms "a," "an," and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. It should also be understood that the term "and/or" as used herein refers to and encompasses any or all possible combinations of one or more of the associated listed items.
It should be understood that although the terms first, second, third, etc. may be used in this specification to describe various information, these information should not be limited to these terms. These terms are only used to distinguish one type of information from another. For example, the first information may also be referred to as second information, and similarly, the second information may also be referred to as first information, without departing from the scope of the present description. The word "if" as used herein may be interpreted as "at … …" or "at … …" or "responsive to a determination", depending on the context.
Banks, enterprises, some third party platforms and the like all need to check the circulating funds of each business transaction so as to ensure the security of the business transaction funds. Taking a payment device as an example, when a user completes a business transaction by using the payment device, the account main bodies associated with the business transaction are required to be determined according to the business type of the business transaction, the fund circulation directions among the account main bodies are checked, and whether the fund circulation directions among the account main bodies and the account main bodies in the transaction data of the business transaction are correct or not is checked. For example, when a user makes a round-robin purchase and pays to a round-robin merchant by using balance treasures, the account body associated with the business transaction is the balance treasures account and the round-robin merchant account of the user, and the fund circulation direction is the fund flow of the balance treasures account of the user into the round-robin merchant account. Meanwhile, after each business transaction occurs, corresponding account running water is generated in an account system corresponding to the account main body and is stored in a corresponding account database, so that whether transaction data in the business transaction are consistent with the account running water in the account database is also required to be checked. For example, when the user pays to the treasured washing merchant by using the balance treasured, the account of the treasured washing merchant must have corresponding financial running water, that is, after each business transaction occurs, the financial running water generated in the account system must be consistent with the transaction data generated in the business system. Currently, when checking funds of each business transaction, checking personnel write checking codes according to understanding and experience of the business to check the business funds. Because the account main body number involved in the business transaction is large, and the business in and out and the fund flow of the account main body are very complex, the verification code can not be written fully by the verification personnel for understanding the business, the whole business chain can not be covered, the verification code is also not well understood, and the management and maintenance are not easy. In addition, the adoption of the checking mode also requires that a checking person is very familiar with the service and can write codes, thereby bringing a plurality of inconveniences.
Based on this, the present description provides a fund checking method, in which a fund checking staff only needs to edit a fund flow diagram matched with a business type in an editing interface, a checking configuration table can be automatically generated according to the edited fund flow diagram, when a checking request is received, the checking configuration table is determined according to the business type of a business transaction to be checked, and then the fund of the business transaction is automatically checked based on the checking configuration table. The check logic of the business is expressed by the graph, then the check configuration table is automatically generated, the operation is simpler and more visual, and the check personnel only need to be familiar with the business logic and do not need to write the check code, so that the fund check is more convenient. Specifically, as shown in fig. 1, the method comprises the following steps:
s102, generating an editing interface so that a user edits a fund flow diagram matched with the business type at the editing interface, wherein the fund flow diagram is used for describing fund circulation relations between account main bodies;
s104, generating and storing a check configuration table according to the fund flow diagram; the check configuration table is used for describing account bodies associated with different service types and the fund circulation direction between the account bodies;
s106, when a checking request is received, determining a checking configuration table of the business transaction based on the business type of the business transaction to be checked, and checking funds of the business transaction based on the checking configuration table.
The fund checking method provided by the embodiment of the specification can be used for various checking systems or checking platforms for checking the fund of the business transaction. The checking system can generate a visual editing interface through which a user can draw a fund flow diagram, wherein the fund flow diagram is used for representing the fund circulation condition of a business transaction, and the fund flow diagram describes an account main body associated with the business transaction and the fund circulation relation among the account main bodies. In general, the relationship between the account body and the account body associated with the same service type is the same, so that when the funds flow diagram is drawn, the funds flow diagram can be divided according to the service types, and one service type is matched with one funds flow diagram. For example, a user uses balance treasures to pay a treasured merchant for a type of service, and the account bodies involved in the service are a user balance treasure account and a treasured merchant account, and funds flow direction is from the user balance treasure account to the treasured merchant account. Generally, a corresponding service identifier is provided for a certain service, so that the service identifier can be used for distinguishing the service types. Taking the service of the payment device as an example, a specific service is generally identified by combining a product code, an event code and a serial number. The product codes divide the business into a plurality of major categories according to the products, one category corresponds to one product code, the event code further subdivides the business under each product code into minor categories, and the serial number is specific to each specific business transaction. Therefore, the business types may be divided by product code or a combination of product code plus event code and the funds flow graph may be edited. For example, a product code corresponds to a funds flow diagram, or a product code+event code corresponds to a funds flow diagram, although other fields may be added to distinguish between product codes and event codes if they are not sufficient to distinguish between service types. In short, matched fund flow diagrams can be drawn according to service types, and the service types can be flexibly divided according to specific requirements.
In some embodiments, as shown in fig. 2, various types of account bodies that may be involved in the business may be preset, and then a designated control, such as an "add account body control", may be provided in the editing interface, through which a desired account body is selected from the preset account bodies and added to the funds flow graph, where the direction of the arrow may be used to indicate the funds flow direction between the account bodies. For example, in the case of paying the panning business with both balance and flowers, the funds flow diagram shown in fig. 2 may be used to represent the funds flow relationship between account bodies.
After the user draws the fund flow graph of one service type, the drawn fund flow graph can be saved by clicking a saving control of the editing interface. After the user clicks the saved fund flow diagram, the checking system generates a checking configuration table according to the fund flow diagram, and the checking configuration table is used for describing account main bodies associated with different service types and fund circulation directions among the account main bodies. The check configuration table records service types which can be represented by product codes and event codes of the service; the account main bodies related to the service types, such as balance treasures, flowers, treasures and trade accounts, and the like, and the corresponding accounting system, accounting mode, accounting database for storing account running water and the like of the account main bodies are also recorded, so that the account running water of the account main bodies can be conveniently inquired according to the information, and the fund circulation direction between the account main bodies is also recorded by checking the configuration table. After generating the reconciliation configuration table from the funds flow diagrams, the reconciliation configuration table may be stored in a database.
When the checking system receives the checking request for checking the funds of the business transaction, the business type of the business transaction to be checked can be determined first, then the checking configuration table corresponding to the business type is inquired in the database storing the checking configuration table, and the funds of the business transaction are checked according to the checking configuration table. In some embodiments, the verification request may be sent by the business system that completes the business transaction to the verification system, e.g., once per business transaction the business system completes. Of course, the business system may also periodically send a verification request to the verification system, with one verification request being used to request the verification system to verify multiple business transactions. In some embodiments, the check request carries detailed transaction data of the business transaction, such as detailed information of a serial number of the business transaction, an account body of the transaction, a circulation direction of funds, a transaction amount, a transaction time and the like. In some embodiments, the verification request may also only include a service identifier, such as a serial number, that identifies the service transaction, and the verification system obtains the service identifier after receiving the verification request, and then obtains detailed transaction data from the service system according to the service identifier. For example, the verification system may obtain the transaction data corresponding to the serial number according to the serial number of the service transaction to the service system.
Since the collation system is to collate data of a plurality of service systems, if a manner in which the service systems transmit collation requests to the collation system is adopted, the collation system needs to interface with the service systems one by one and consider access manners according to characteristics of the respective service systems, which makes fund collation complicated to some extent due to considering the interface manner of the collation system with each service system. Thus, in some embodiments, the reconciliation system may subscribe to an accounting database and the reconciliation request may be triggered by a data change event in the accounting database. As each business transaction is completed in the business system, the account body associated with the business transaction generates corresponding financial running water and stores the corresponding financial running water in a corresponding financial database. Therefore, as soon as the data in the accounting database is changed, a new business transaction is indicated to occur, and the check request can be automatically triggered. The checking system subscribes to the account database, and the data of the account database is changed to automatically trigger the checking request, so that the checking system does not need to access the service system one by one through codes, and the pressure of the service system is reduced to a certain extent.
After receiving the verification request, the verification system can determine a verification configuration table according to the service type of the service transaction to be verified, acquire transaction data of the service transaction, extract an associated account main body from the transaction data, determine information such as an accounting system, an accounting mode, an accounting database for storing accounting running water and the like corresponding to the account main body according to the verification configuration table, and then inquire the accounting running water corresponding to the service transaction of the account main body according to the information. Because the checking configuration table is used for verifying the account main body and the funds circulation direction which are related to the business transaction, the account main body and the funds circulation direction of the business transaction described in the transaction data can be compared with the account main body and the funds circulation direction described in the checking configuration table in the checking process, whether the account main body and the funds circulation direction are consistent is verified, and whether the funds circulation direction and the funds circulation direction of the account main body described in the transaction data are consistent with the funds circulation direction and the funds circulation direction of the account main body described in the account circulation is verified, if the two parts of contents are consistent, the funds of the business transaction are not problematic, and if the two parts of contents are inconsistent, the funds of the business transaction are problematic. After the collation is completed, the collation result may be output. For example, suppose that a user uses balance and a cut to pay to a treasured-washing merchant together, the balance pays 200 yuan, the cut pays 100 yuan, and after the user finishes paying, the treasured-washing system generates transaction data of the transaction, wherein the transaction data comprises transaction time, transaction serial number, transaction account main body (user balance account, cut account and treasured-washing merchant account) of the transaction, and fund flow and amount of the transaction (the user balance account pays 200 yuan to the merchant account and the user cut account pays 100 yuan to the merchant account). The collation system may obtain the transaction data based on the serial number of the transaction carried by the collation request. The collation system may then determine a collation configuration table based on the business type of the business. The checking configuration table records account main bodies (user balance treasures, user's bar, and treasured merchant account numbers) related to the business exchange of the type, and records relevant information of the account main bodies, such as corresponding accounting systems, accounting modes and the like. The checking system can acquire the accounting running water of the three account main bodies, such as the accounting running water of balance treasures of the users, the accounting running water of the treasures-washing merchants according to the information recorded by the checking configuration table. And then the checking system checks whether the account main body and the fund flow related to the transaction data are consistent with those recorded in the checking configuration table, namely, whether the account main body comprises a user balance treasures, a user's water and a treasured trade company account, and then the fund flow in the transaction data is consistent with those recorded in the checking configuration table, namely, whether the user balance treasures flows into the treasured trade company account and the user's water flows into the treasured trade company account. Then, the checking system also needs to check whether the information of the transaction data is consistent with the information of the account flow, such as whether the user balance is checked out by 200 yuan to the treasured merchant account, whether the user spends by 100 yuan to the treasured merchant account, whether the treasured merchant account is checked in by 200 yuan from the user balance and checked in by 100 yuan from the user balance, if the two parts of information are consistent, the fund of the business transaction is not problematic.
In the prior art, since the fund check of the business transaction is completed by checking personnel writing codes, when the account main body or the fund circulation relation of a certain type of business is changed, the codes need to be modified again so as to conform to the current business logic. The maintenance and management of the code is very inconvenient. In some embodiments of the present disclosure, if the logic of the service is changed, for example, in a service transaction, an associated account body is added or reduced, or the circulation relationship of funds is changed, the matched funds flow diagram of the service may be directly modified, and then the verification system may update and store the verification configuration table according to the modified funds flow diagram. By adopting the checking method provided by the specification, the checking configuration table of the service can be conveniently modified, the checking code is not required to be directly modified, and the maintenance and the management are convenient.
In order to further explain the fund checking method provided in the present specification, a specific embodiment will be described below.
The payment treasures are used as a third party payment platform and involve a large amount of business funds circulation every day. To ensure funds security, each business funds must be checked. The embodiment of the specification provides a fund checking system and a fund checking method, which only need fund checking personnel to edit a fund flow diagram of a service in an editing interface according to service logic, then a checking configuration table can be automatically generated and stored, when the checking system receives a checking request, the checking configuration table can be determined according to the type of the service transaction to be checked, and the service transaction can be checked according to the checking configuration table.
As shown in fig. 3, the checking system may provide an editing interface through which a user may draw a funds flow diagram, where the editing interface includes an account body possibly associated with a preset business transaction, and a control for "adding a participant" is further included on the editing interface, through which the user may add the account body, and of course, the user may also directly drag the account body displayed on the left side of the editing interface to the funds flow diagram drawing area, where the funds flow diagram describes a funds flow direction between the account body associated with the business transaction and the account body, where the funds flow direction may be indicated by an arrow. Since the fund flow diagrams of the same service type are the same, the fund flow diagrams can be divided according to the service type when being drawn, the service type can be expressed by a product code and an event code, and one product code is combined with one event code to serve as one service and match one fund flow diagram. After the fund flow diagram is drawn, the user can click a save button of the editing interface, and then the fund flow diagram can be saved.
Meanwhile, the checking system generates and stores a checking configuration table based on a fund flow diagram drawn by a user, wherein the checking configuration table is shown in fig. 4, the 'fund flow configuration' records main fields, the contents of each field are recorded through an extended table, the checking configuration table generally records service types, the service types are represented by product codes and event codes, the checking configuration table also records account bodies associated with service transactions, and particularly comprises account bodies and information related to the account bodies, such as an accounting system, an accounting mode and the like corresponding to the account bodies, and the account flow of the account bodies can be queried according to the information. The reconciliation configuration table also records the direction of funds transfer between account bodies.
As shown in fig. 5, when a business transaction is completed in the business system 51, the account body associated with the business transaction adds an accounting stream, and the accounting stream is stored in the accounting database 52. After the business transaction is completed, the accounting database 52 will be newly added with the corresponding accounting stream for the business transaction. The checking system 53 may subscribe to the accounting database 52, and when the data in the accounting database 52 is changed, that is, when accounting running water is newly added, the checking request may be automatically triggered and sent to the checking system 53, where the checking request carries the running number of the business transaction. After receiving the verification request, the verification system 53 obtains the transaction data of the transaction from the serial number business system 51, extracts the associated account body from the transaction data, then determines the product code and the event code of the business transaction to obtain a pre-stored verification configuration table, and obtains the accounting flow of the account body according to the accounting system and other information of the account body recorded in the verification configuration table. The checking system 53 checks whether the account main body and the account main body funds circulation direction recorded in the transaction data are consistent with the account main body and funds circulation direction recorded in the checking configuration table, and the checking system 53 also needs to check whether the funds flow direction and the amount of funds of the account main body in the transaction data are consistent with the accounting running water of the account main body. After the verification is completed, a verification result is output to the user.
Because the account bodies of the assets related to the payment treasures are relatively more, such as balance treasures, balances, flowers, red packages, collection treasures, credit cards and the like, when the fund flow diagrams are drawn, if the account bodies of the assets are combined, the combination mode reaches hundreds, in order to simplify the account bodies and avoid drawing hundreds of fund flow diagrams, the account bodies of the assets can be collectively called as assets, and as shown in fig. 6, the account bodies and various combinations thereof are replaced by the assets. The information about these assets is then recorded exclusively with a checkup configuration table of assets, which then records only the information about the internal intermediate account and the payee account. When a reconciliation request is received, on the one hand, which of the associated assets are to be extracted from the transaction data of the transaction, and then the asset is reconciled by looking up a reconciliation configuration table of the asset based on the identity of the asset. On the other hand, other related account main bodies except the assets can be extracted from the transaction data, the checking configuration table is determined according to the type of the business transaction, and the other related account main bodies are checked according to the checking configuration table.
The various technical features in the above embodiments may be arbitrarily combined as long as there is no conflict or contradiction between the combinations of the features, but are not described in detail, so that the arbitrary combination of the various technical features in the above embodiments also falls within the scope of the disclosure of the present specification.
As shown in fig. 7, which is a funds checking apparatus corresponding to the funds checking method described above, the apparatus 70 may include:
the interface display module 71 generates an editing interface so that a user edits a fund flow graph matched with the service type at the editing interface, wherein the fund flow graph is used for describing the fund circulation relation between account bodies;
a configuration module 72 for generating and storing a check configuration table according to the fund flow graph; the check configuration table is used for describing account bodies associated with different service types and the fund circulation direction between the account bodies;
the collation module 73, when receiving the collation request, determines a collation configuration table of the business transaction based on the business type of the business transaction to be collated, and collates funds of the business transaction based on the collation configuration table.
In one embodiment, reconciling funds for the business transaction based on the reconciliation configuration table comprises:
extracting an account body associated with the business transaction from transaction data of the business transaction;
acquiring account running water of the account main body based on the check configuration table;
and checking whether the fund circulation direction between the account main body and the account main body described by the check configuration table is consistent with the transaction data or not, and whether the accounting flow is consistent with the transaction data or not.
In one embodiment, the reconciliation request carries a service identifier of the service transaction, and the transaction data is obtained based on the service identifier.
In one embodiment, the reconciliation request is triggered based on a data change event in an accounting database that is used to store accounting flowing of the account body.
In one embodiment, when the funds flow graph is updated, the corresponding checklist configuration table of the funds flow graph is updated based on the updated funds flow graph.
In one embodiment, the editing interface includes a designated control for adding the account bodies, the direction of funds flow between the account bodies being indicated by the pointing direction of the arrow.
Specific details of the implementation process of the functions and roles of each module in the device are shown in the implementation process of the corresponding steps in the method, and are not repeated here.
For the device embodiments, reference is made to the description of the method embodiments for the relevant points, since they essentially correspond to the method embodiments. The apparatus embodiments described above are merely illustrative, wherein the modules illustrated as separate components may or may not be physically separate, and the components shown as modules may or may not be physical, i.e., may be located in one place, or may be distributed over a plurality of network modules. Some or all of the modules may be selected according to actual needs to achieve the purposes of the present description. Those of ordinary skill in the art will understand and implement the present invention without undue burden.
Embodiments of the present description apparatus may be applied to a computer device, such as a server or a smart terminal. The apparatus embodiments may be implemented by software, or may be implemented by hardware or a combination of hardware and software. Taking software implementation as an example, the device in a logic sense is formed by reading corresponding computer program instructions in the nonvolatile memory into the memory through a processor of the file processing where the device is located. In terms of hardware, as shown in fig. 8, a hardware structure diagram of a computer device where the apparatus of the present disclosure is located is shown in fig. 8, and in addition to the processor 802, the memory 804, the network interface 806, and the nonvolatile memory 808 shown in fig. 8, a server or an electronic device where the apparatus is located in the embodiment may generally include other hardware according to the actual function of the computer device, which will not be described herein.
Accordingly, the present specification embodiment also provides a computer storage medium having a program stored therein, which when executed by a processor, implements the method in any of the above embodiments.
Accordingly, the present description also provides a computer device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, the processor implementing the method of any of the above embodiments when executing the program.
The present application may take the form of a computer program product embodied on one or more storage media (including, but not limited to, magnetic disk storage, CD-ROM, optical storage, etc.) having program code embodied therein. Computer-usable storage media include both permanent and non-permanent, removable and non-removable media, and information storage may be implemented by any method or technology. The information may be computer readable instructions, data structures, modules of a program, or other data. Examples of storage media for a computer include, but are not limited to: phase change memory (PRAM), static Random Access Memory (SRAM), dynamic Random Access Memory (DRAM), other types of Random Access Memory (RAM), read Only Memory (ROM), electrically Erasable Programmable Read Only Memory (EEPROM), flash memory or other memory technology, compact disc read only memory (CD-ROM), digital Versatile Disks (DVD) or other optical storage, magnetic cassettes, magnetic tape magnetic disk storage or other magnetic storage devices, or any other non-transmission medium, may be used to store information that may be accessed by the computing device.
In addition, the present application further provides a system architecture for fund checking, as shown in fig. 9A, where the system architecture includes: accounting database 91 and checking system 92,
the accounting database 91 is configured to store accounting flowing water of an account main body, and when the accounting flowing water is changed, trigger a checking request and send the checking request to the checking system 92;
the checking system 92 is configured to generate an editing interface 921, so that a user edits a funds flow sheet matched with a service type in the editing interface 921, where the funds flow sheet is used to describe a funds flow relationship between account bodies; generating and storing a check configuration table according to the fund flow graph; the check configuration table is used for describing account bodies associated with different service types and the fund circulation direction between the account bodies; when the check request is received, a check configuration table of the business transaction is determined based on the business type of the business transaction to be checked, and funds of the business transaction are checked based on the check configuration table.
In one embodiment, as shown in fig. 9B, the system architecture further comprises: the business system 93 is configured to generate and store transaction data of a business transaction after completing the business transaction, and the verification system obtains the transaction data from the business system and extracts an account body associated with the business transaction from the transaction data of the business transaction after receiving the verification request; acquiring account running water of the account main body based on the check configuration table; and checking whether the fund circulation direction between the account main body and the account main body described by the check configuration table is consistent with the transaction data or not, and whether the accounting flow is consistent with the transaction data or not.
Other embodiments of the disclosure will be apparent to those skilled in the art from consideration of the specification and practice of the disclosure herein. This disclosure is intended to cover any adaptations, uses, or adaptations of the disclosure following the general principles of the disclosure and including such departures from the present disclosure as come within known or customary practice within the art to which the disclosure pertains. It is intended that the specification and examples be considered as exemplary only, with a true scope and spirit of the disclosure being indicated by the following claims.
It is to be understood that the present disclosure is not limited to the precise arrangements and instrumentalities shown in the drawings, and that various modifications and changes may be effected without departing from the scope thereof. The scope of the present disclosure is limited only by the appended claims.
The foregoing description of the preferred embodiments of the present disclosure is not intended to limit the disclosure, but rather to cover all modifications, equivalents, improvements and alternatives falling within the spirit and principles of the present disclosure.