CN110738477B - Account checking method and device, computer equipment and storage medium - Google Patents
Account checking method and device, computer equipment and storage medium Download PDFInfo
- Publication number
- CN110738477B CN110738477B CN201910776689.XA CN201910776689A CN110738477B CN 110738477 B CN110738477 B CN 110738477B CN 201910776689 A CN201910776689 A CN 201910776689A CN 110738477 B CN110738477 B CN 110738477B
- Authority
- CN
- China
- Prior art keywords
- reconciliation
- bill
- comparison
- processing result
- data
- 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
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/08—Payment architectures
- G06Q20/10—Payment architectures specially adapted for electronic funds transfer [EFT] systems; specially adapted for home banking systems
- G06Q20/102—Bill distribution or payments
-
- 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
Abstract
The invention discloses a reconciliation method, a reconciliation device, computer equipment and a readable storage medium. The method comprises the steps of obtaining an unsettled reconciliation task from a reconciliation database; acquiring the payment center configuration of a current payment center, and judging the reconciliation type of the reconciliation task according to the payment center configuration; acquiring a bill to be checked from a local database, and performing checking processing on the bill to be checked according to the checking type to obtain a checking processing result; when the account checking processing result accords with a preset account checking processing result, checking a leveling task processing result of an acceptance mechanism corresponding to the current payment center; and if the leveling task processing result is that all leveling tasks of the acceptance mechanism are leveled, generating an acceptance mechanism statement, and pushing the acceptance mechanism statement to a private cloud. By adopting the method, the technical problem of low account checking efficiency in the prior art is solved.
Description
Technical Field
The present application relates to the field of data processing technologies, and in particular, to a reconciliation method, apparatus, computer device, and storage medium.
Background
The amount, time and bill state theory of the enterprise bank bill and the bill issued by the bank should be consistent, but in a special case, the accounts of the two parties are not consistent, and the day knot of the merchant generated based on the order of the bill has a gap. In the conventional technology, bills generated by daily transactions need to be checked, but because of different types of generated bills, the modes of checking bills are different, generally when the bills are checked, the modes of checking bills of different types are often the same, and for different types of checking bills, a certain step may be absent or redundant in the checking mode, which leads to low efficiency of checking bills.
Disclosure of Invention
The embodiment of the invention provides an account checking method, an account checking device, computer equipment and a storage medium, and aims to solve the technical problem of low account checking efficiency caused by single account checking mode in the prior art.
A reconciliation method comprising:
acquiring an unsettled reconciliation task from a reconciliation database; acquiring the payment center configuration of a current payment center, and judging the account checking type of the account checking task according to the payment center configuration; acquiring a to-be-checked bill from a local database, and performing checking processing on the to-be-checked bill according to the checking type to obtain a checking processing result; when the reconciliation processing result accords with a preset reconciliation processing result, checking a reconciliation task processing result of an acceptance mechanism corresponding to the current payment center; and if the leveling task processing result indicates that all the leveling tasks of the acceptance mechanism are leveled, generating an acceptance mechanism statement bill, and pushing the acceptance mechanism statement bill to a private cloud.
A reconciliation apparatus comprising:
the acquisition module is used for acquiring the account checking tasks which are not checked from the account checking database; the judging module is used for acquiring the payment center configuration of the current payment center and judging the account checking type of the account checking task according to the payment center configuration; the account checking module is used for acquiring an account checking bill to be checked from a local database, and performing account checking processing on the account checking bill to be checked according to the account checking type to obtain an account checking processing result; the checking module is used for checking the reconciliation task processing result of the acceptance mechanism corresponding to the current payment center when the reconciliation processing result accords with a preset reconciliation processing result; and the pushing module is used for generating a checking bill of the acceptance mechanism and pushing the checking bill of the acceptance mechanism to the private cloud if the checking task processing result is that all the checking tasks of the acceptance mechanism are checked.
A computer device comprising a memory and a processor, and a computer program stored in the memory and executable on the processor, the processor implementing the steps of the above reconciliation method when executing the computer program.
A computer-readable storage medium, in which a computer program is stored which, when being executed by a processor, carries out the steps of the above-mentioned reconciliation method.
According to the account checking method, the account checking device, the computer equipment and the readable storage medium, the payment center configuration is set in the payment center in advance, the account checking type of the account checking task is judged according to the payment center configuration, the account checking is carried out according to different account checking types, and the generated acceptance mechanism account checking bill is pushed to the private cloud according to the account checking result which accords with the preset result.
Drawings
In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings used in the description of the embodiments of the present invention will be briefly introduced below, and it is obvious that the drawings in the following description are only some embodiments of the present invention, and it is obvious for those skilled in the art that other drawings can be obtained according to these drawings without inventive labor.
FIG. 1 is a diagram of an application environment of the reconciliation method in one embodiment;
FIG. 2 is a flow diagram illustrating a reconciliation method in one embodiment;
FIG. 3 is a schematic flow chart of step 206 of FIG. 2;
FIG. 4 is another schematic flow chart of step 206 of FIG. 2;
FIG. 5 is a schematic flow chart of step 404 in FIG. 4;
FIG. 6 is a flow chart illustrating a reconciliation method according to another embodiment;
FIG. 7 is a schematic view of a reconciliation apparatus;
FIG. 8 is a diagram of a computer device in one embodiment.
Detailed Description
Unless defined otherwise, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this application belongs; the terminology used in the description of the application herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the application; the terms "comprising" and "having," and any variations thereof, in the description and claims of this application and the description of the above figures, are intended to cover non-exclusive inclusions. The terms "first," "second," and the like in the description and claims of this application or in the foregoing drawings are used for distinguishing between different objects and not for describing a particular order.
Reference herein to "an embodiment" means that a particular feature, structure, or characteristic described in connection with the embodiment can be included in at least one embodiment of the application. The appearances of the phrase in various places in the specification are not necessarily all referring to the same embodiment, nor are separate or alternative embodiments mutually exclusive of other embodiments. It is explicitly and implicitly understood by one skilled in the art that the embodiments described herein can be combined with other embodiments.
In order to make the objects, technical solutions and advantages of the present application more apparent, the present application will be further described in detail with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative of the present application and are not intended to limit the present application. All other embodiments, which can be obtained by a person skilled in the art without any inventive step based on the embodiments of the present invention, are within the scope of the present invention.
The reconciliation method provided by the embodiment of the invention can be applied to the application environment shown in FIG. 1. The application environment may include a terminal 102, a network 106, and a server 104, where the network 106 is used to provide a communication link medium between the terminal 102 and the server 104, and the network 106 may include various connection types, such as wired, wireless communication links, or fiber optic cables.
A user may use the terminal 102 to interact with the server 104 over the network 106 to receive or send messages, etc. Various communication client applications, such as a web browser application, a shopping application, a search application, an instant messaging tool, a mailbox client, social platform software, etc., may be installed on the terminal 102.
The terminal 102 may be various electronic devices having a display screen and supporting web browsing, including but not limited to a smart phone, a tablet computer, an e-book reader, an MP3 player (Moving Picture Experts Group Audio Layer III, mpeg compression standard Audio Layer 3), an MP4 player (Moving Picture Experts Group Audio Layer IV, mpeg compression standard Audio Layer 4), a laptop portable computer, a desktop computer, and the like.
The server 104 may be a server that provides various services, such as a backend server that provides support for pages displayed on the terminal 102.
It should be noted that the reconciliation method provided in the embodiment of the present application is generally executed by a server/terminal, and accordingly, the reconciliation apparatus is generally disposed in the server/terminal device.
It should be understood that the number of terminals, networks and servers in fig. 1 is merely illustrative. There may be any number of terminal devices, networks, and servers, as desired for implementation.
Wherein, the terminal 102 communicates with the server 104 through the network. After receiving the reconciliation task, the server 104 acquires a to-be-reconciled bill from the terminal 102, and performs reconciliation processing on the to-be-reconciled bill to obtain a reconciliation processing result; and then analyzing the account checking processing result to see whether the account checking processing result meets a preset condition, if so, generating an account handling mechanism account check for the account checking bill according to preset mechanism account check pushing configuration, and sending the account handling mechanism account check to a private cloud. The terminal 102 and the server 104 are connected through a network, the network may be a wired network or a wireless network, the terminal 102 may be, but is not limited to, various personal computers, notebook computers, smart phones, tablet computers, and portable wearable devices, and the server 104 may be implemented by an independent server or a server cluster formed by a plurality of servers.
In an embodiment, as shown in fig. 2, an account reconciliation method is provided, which is described by taking the application of the method to the server in fig. 1 as an example, and includes the following steps:
The payment platform needs to generate a reconciliation task with the channel partner Id of the third party, namely the merchant number, as a dimension so as to ensure that the bill is accurate, and then the reconciliation task is supplied to the merchant or the channel needing to download the merchant reconciliation bill. The reconciliation database stores a reconciliation task needing reconciliation, and the reconciliation task can be generated at regular time every day or according to the needs of the merchant. The server can then retrieve reconciliation tasks from the reconciliation database that have not been reconciled.
And 204, acquiring the payment center configuration of the current payment center, and judging the reconciliation type of the reconciliation task according to the payment center configuration.
Current payment centers are the IDs of the third party's channel partners, i.e., merchant numbers. The payment center configuration is divided according to the corresponding business type of the merchant number. If a certain institution cannot acquire an interface of a certain account data of a certain payment platform directly transferring to a certain merchant, an account checking mode suitable for the situation needs to be generated to count the daily account of the merchant or accept the account checking of the institution. The tie-out types may be tie-out, local tie-out, and third party tie-out. And under the condition that the bill data of a certain payment platform cannot be obtained, the statement of the acceptance mechanism or the daily account of the merchant can be generated only by taking the order data local to the merchant as the standard.
And step 206, acquiring the account to be checked bill from the local database, and performing account checking on the account to be checked bill according to the account checking type to obtain an account checking processing result.
The database of the local data on the Server for storing the bill data can be realized by the existing general databases, the types of the usable databases are more, the traditional commercial databases including DB2, oracle, SQL Server and the like can be used, and the open source database such as MySQL and the like can also be used; the system comprises a relational database, unstructured Hadoop and Spark platforms, and a distributed cache platform based on Redis (open source, written by using ANSIC language, supporting network, and a log-type and Key-Value database which can be based on memory and can also be persisted) for supplementing the relational database.
And after the account checking bill to be checked is obtained, selecting a corresponding account checking mode for the account checking bill to be checked according to the determined account checking type of the account checking task, and performing account checking processing to obtain an account checking processing result.
And 208, checking a reconciliation task processing result of the acceptance mechanism corresponding to the current payment center when the reconciliation processing result meets a preset reconciliation processing result.
If the reconciliation processing result is the reconciliation bill to be reconciled, and the reconciliation bill to be reconciled is correct, the reconciliation processing result can be considered to be in accordance with the preset reconciliation processing result, and then the condition of the reconciliation task processing result on the handling mechanism corresponding to the current payment center is checked.
And step 210, if the leveling task processing result is that all the leveling tasks of the acceptance mechanism are leveled, generating an account checking list of the acceptance mechanism, and pushing the account checking list of the acceptance mechanism to a private cloud.
Because more than one account checking task is needed, all account checking tasks need to be checked before generating the statement of the acceptance mechanism, and if the account checking tasks which are not processed exist, the account checking processing is continued; and if the reconciliation task on the acceptance mechanism is completely finished, pulling the preset mechanism statement of account push configuration, generating an acceptance mechanism statement of account according to the preset mechanism statement of account push configuration and the statement of account to be reconciled, and pushing the acceptance mechanism statement of account to the private cloud storage so as to facilitate the downloading and use of the current payment center.
According to the account checking method, the payment center is arranged in the payment center in advance, the account checking type of the account checking task is judged according to the configuration of the payment center, account checking is carried out according to different account checking types, and the account checking result according with the preset result is pushed to the private cloud to carry out account checking of an acceptance mechanism.
In one embodiment, as shown in FIG. 3, step 206, comprises:
and 302, when the reconciliation type is third-party reconciliation, acquiring a third-party bill as a to-be-reconciled bill, and analyzing the to-be-reconciled bill to obtain to-be-reconciled data.
And when the reconciliation type is third-party reconciliation, directly downloading a third-party bill from a bill database of a third-party platform, analyzing the third-party bill to obtain a core field in the third-party bill as to-be-leveled data, wherein the to-be-leveled data comprises the to-be-leveled amount, the to-be-leveled time and the to-be-leveled order state. The bill not only includes the data to be leveled including the amount of the money to be leveled, the time to be leveled and the status of the order to be leveled, but also includes an order number, an order destination and the like, which are not described herein again.
And step 304, taking a preset account checking processing result as an account checking processing result.
And if the reconciliation type is the third-party reconciliation, the reconciliation treatment is not carried out on the reconciliation bill, but the preset reconciliation treatment result is directly used as the reconciliation treatment result of the current reconciliation.
In addition, the acceptance agency statement in step 210 is generated based on the data to be reconciled. The data to be leveled can be used as basic data for generating the daily knot of the merchant besides generating the statement of the acceptance mechanism.
The mechanism statement of account pushing configuration generates configuration data of the statement of account of the mechanism according to the mode. In this embodiment, the institution-to-bill pushing configuration is that the server generates an institution-to-bill according to the obtained data to be leveled, and sends the generated institution-to-bill to the private cloud.
Furthermore, the institution statement of account handling can be directly generated according to the statement of account to be checked corresponding to the data to be checked, and the institution statement of account handling data generated according to the statement of account to be checked is more detailed. But the data of the account checking list of the acceptance mechanism generated according to the data to be checked is more compact.
The bill checking of the acceptance mechanism comprises the steps that after all account checking tasks under the acceptance mechanism are completed, order data of third-party data are pulled, namely, the flat data are written into a file with a preset format, the file is encrypted through an AES (advanced encryption standard) and signed, and the file is pushed to a private cloud. The purpose of carrying out encryption signature is to ensure the data security and accuracy in the data transmission process.
Further, the file naming format may be a comma separated value (csv) file. Specifically, as shown in table 1:
| serial number | Column name | Remarks for note |
| 1 | Type of order | The forward order is success; back order refund |
| 2 | Transaction time | Time of transaction success |
| 3 | Number of acceptance mechanism | Order number of acceptance institution |
| 4 | Merchant Id | Numbering at the Wenfuton Merchant platform |
| 5 | Amount of transaction | The payment order is the transaction amount and the refund is the refund amount |
| 6 | Order status | 2/4/1/3/8/9 |
TABLE 1
According to the method and the device, the bill of the acceptance mechanism is generated directly on the basis of the data of the bill of the third party by acquiring the bill of the third party, the step of account checking processing is omitted, the time of data processing is greatly reduced, and the efficiency of generating the bill of the acceptance mechanism is improved.
In one embodiment, step 206, comprises:
and when the reconciliation type is local reconciliation, acquiring a local order from the local database as a to-be-reconciled bill, and taking a preset reconciliation processing result as a reconciliation processing result.
And if the reconciliation type is local reconciliation, directly acquiring local order data of the merchant from the local database, and taking a preset reconciliation processing result with the reconciliation list to be the reconciliation result as a reconciliation processing result.
Further, the acceptance agency statement in step 210 is generated from the local order.
The server directly generates an acceptance mechanism statement according to the local order data and then pushes the statement to the private cloud for storage.
In the embodiment, the third-party bill does not need to be pulled for reconciliation, but the merchant is finished daily or the acceptance mechanism is used for reconciliation and clearing, so that the pressure of a server for excessive reconciliation processing is reduced.
In one embodiment, as shown in FIG. 4, step 206, comprises:
and 402, when the reconciliation type is contrast reconciliation, acquiring a third party bill as a to-be-reconciled bill, and analyzing the to-be-reconciled bill to obtain to-be-reconciled data.
The account checking can adopt system memory account checking, all bills are loaded into the memory for account checking at one time, and the pressure of an account checking database can be reduced. And when the account checking type is the contrast account checking, downloading the third party bill as the bill to be checked and searching a local order consistent with the order number of the third party bill from the local database. After the local order is obtained, the third-party account is analyzed to obtain a core field: the information of money amount, time, state and the like is used as the data to be leveled.
And step 404, acquiring comparison reconciliation data of the corresponding local order, and performing consistency comparison on the reconciliation data to be reconciled with the comparison reconciliation data to obtain a reconciliation processing result.
Analyzing the obtained local order to obtain a core field of the local order, taking information such as money amount, time, state and the like as comparison reconciliation data, and then carrying out consistency comparison on the data to be reconciled and the attribute data in the comparison reconciliation data one by one to obtain a reconciliation processing result.
Specifically, the reconciliation processing result may be: data that is present on the local order but not on the third party bill, not on the local order but on the third party bill, as well as data that is both on the local bill and the third party bill, but also on the local bill, the third party bill, but on the local order and the third party bill, as well as on the local order and the third party bill. And the amount of the order transaction is consistent to the preset reconciliation processing result according to the data on the local order and the third-party bill. If the amount result of the local order is inconsistent with that of the third party order, the amount data of the third party order needs to be adjusted to obtain a consistent result.
In addition, the acceptance agency statement in step 210 may be generated based on the data to be reconciled.
And when the condition that all the leveling tasks are leveled is met, processing the data to be leveled according to the mechanism statement push configuration to generate an acceptance mechanism statement, and then pushing the statement to a private cloud for storage.
In the embodiment, the third-party bill and the local order are downloaded to compare data item by item, the reconciliation processing result of task statistics, abnormal record lists or bill reconciliation is given out, and then the merchant daily knot or the handling mechanism reconciliation bill with the merchant and the payment type as dimensions is generated according to the reconciliation processing result and the handling condition of the reconciliation task, so that the accuracy of the handling mechanism reconciliation bill is improved.
In one embodiment, as shown in FIG. 5, step 404 includes:
The amount to be paid may be amount data such as payment amount, refund amount, etc., the time to be paid may be the time of generating a bill, and the state of the to-be-paid order may be the payment state of the current order.
The comparison amount may be amount data such as payment amount, refund amount, etc., the comparison time may be the time of generating a bill, and the comparison order state may be the payment state of the current order.
And step 508, comparing the consistency of the to-be-leveled time and the comparison time to obtain a time comparison result.
And step 510, carrying out consistency comparison on the state of the flat order to be compared with the state of the comparison order to obtain a state comparison result.
And step 512, integrating the money amount comparison result, the time comparison result and the state comparison result to obtain a reconciliation processing result.
And if the obtained money amount comparison result, the time comparison result and the state comparison result are all consistent, the reconciliation processing result is considered to be a bill reconciliation.
According to the embodiment, the consistency comparison is carried out on various attribute data in the third party bill and the local order, so that the abnormal condition of the order can be obtained more accurately.
In one embodiment, as shown in fig. 6, before step 202, the method further includes:
The server generates reconciliation tasks regularly every day with payment center dimension. For example, the server is daily in the morning 01:00, creating a reconciliation task in the dimension of a payment center, wherein the core field of the reconciliation task is as follows: task Id/time/merchant number.
And step 604, inquiring the account checking task which is not checked from the account checking database according to a preset condition.
The preset condition may be a preset task index field, such as a merchant number. And inquiring the unsettled reconciliation task associated with the merchant number from the database according to the merchant number.
According to the embodiment, the checking task is automatically created every day, so that the accepting mechanism needing the bill can be ensured to generate the checking bill of the accepting mechanism according to the checking task every day in time.
It should be understood that although the steps in the flowcharts of fig. 2-7 are shown in order as indicated by the arrows, the steps are not necessarily performed in order as indicated by the arrows. The steps are not performed in a strict order unless explicitly stated herein, and may be performed in other orders. Moreover, at least some of the steps in fig. 2-7 may include multiple sub-steps or multiple stages that are not necessarily performed at the same time, but may be performed at different times, and the order of performing the sub-steps or stages is not necessarily sequential, but may be performed in turn or alternately with other steps or at least some of the sub-steps or stages of other steps.
In one embodiment, as shown in fig. 7, a reconciliation apparatus is provided, which corresponds to the reconciliation method in the above embodiment one to one. The reconciliation device comprises an acquisition module 802, a judgment module 804, a judgment module 806, an examination module 808 and a push module 710, wherein:
an obtaining module 702 is configured to obtain an unsettled reconciliation task from the reconciliation database.
The determining module 704 is configured to obtain a payment center configuration of a current payment center, and determine a reconciliation type of the reconciliation task according to the payment center configuration.
And the reconciliation module 706 is configured to acquire a to-be-reconciled bill from the local database, and perform reconciliation processing on the to-be-reconciled bill according to the reconciliation type to obtain a reconciliation processing result.
The checking module 708 is configured to check a reconciliation task processing result of the acceptance mechanism corresponding to the current payment center when the reconciliation processing result meets a preset reconciliation processing result.
And a pushing module 710, configured to generate an acceptance mechanism statement and push the acceptance mechanism statement to a private cloud if the result of the leveling task processing is that all leveling tasks of the acceptance mechanism are leveled.
Further, this reconciliation device still includes:
a creating module 712 for creating a reconciliation task.
And the query module 714 is used for querying the account checking tasks which are not checked in the account checking database according to preset conditions.
Further, the reconciliation module 706 is further configured to:
when the reconciliation type is third-party reconciliation, acquiring a third-party bill as a to-be-reconciled bill, and resolving the to-be-reconciled bill to obtain to-be-reconciled data; taking a preset account checking processing result as an account checking processing result; the statement of the generation acceptance mechanism is generated according to the data to be leveled.
Further, the reconciliation module 706 is further configured to:
when the reconciliation type is local reconciliation, acquiring a local order from a local database as a to-be-reconciled bill, and taking a preset reconciliation processing result as a reconciliation processing result; the generated bill is generated by the acceptance institution according to the local order.
Further, the reconciliation module 706 is further configured to:
when the reconciliation type is a contrast reconciliation, acquiring a third party bill as a to-be-reconciled bill, and analyzing the to-be-reconciled bill to obtain to-be-reconciled data; acquiring contrast leveling data of a corresponding local order, and performing consistency comparison on the to-be-leveled data and the contrast leveling data to obtain a reconciliation processing result; the generation of the bill of the acceptance mechanism is generated according to the data to be leveled.
Further, the reconciliation module 706 is further configured to:
inquiring a local order corresponding to the order number of the third party bill from a local database; and acquiring contrast leveling data of the inquired local order.
Further, the reconciliation module 706 is further configured to:
acquiring the to-be-leveled fund amount, the to-be-leveled time and the to-be-leveled order state in the to-be-leveled data; acquiring comparison amount, comparison time and comparison order state in comparison flat data; carrying out consistency comparison on the amount to be leveled and the comparison amount to obtain an amount comparison result; comparing the consistency of the time to be compared with the comparison time to obtain a time comparison result; carrying out consistency comparison on the status of the to-be-paired flat orders and the status of the comparison orders to obtain a status comparison result; and integrating the money amount comparison result, the time comparison result and the state comparison result to obtain the reconciliation processing result.
According to the account checking device, the payment center is arranged in the payment center in advance, account checking types of account checking tasks are judged according to the configuration of the payment center, account checking is carried out according to different account checking types, and account checking results meeting preset results are pushed to the private cloud to send handling mechanism account checking bills.
In one embodiment, a computer device is provided, which may be a server, and its internal structure diagram may be as shown in fig. 8. The computer device includes a processor, a memory, a network interface, and a database connected by a system bus. Wherein the processor of the computer device is configured to provide computing and control capabilities. The memory of the computer device comprises a nonvolatile storage medium and an internal memory. The non-volatile storage medium stores an operating system, a computer program, and a database. The internal memory provides an environment for the operation of an operating system and computer programs in the non-volatile storage medium. The database of the computer device is used for storing user order data. The network interface of the computer device is used for communicating with an external terminal through a network connection. The computer program is executed by a processor to implement a reconciliation method.
As will be understood by those skilled in the art, the computer device is a device capable of automatically performing numerical calculation and/or information processing according to instructions set in advance or stored in advance, and the hardware includes, but is not limited to, a microprocessor, an Application Specific Integrated Circuit (ASIC), a Programmable Gate Array (FPGA), a Digital Signal Processor (DSP), an embedded device, and the like.
It will be appreciated by those skilled in the art that the configuration shown in fig. 8 is a block diagram of only a portion of the configuration associated with the present application, and is not intended to limit the computing device to which the present application may be applied, and that a particular computing device may include more or fewer components than shown, or may combine certain components, or have a different arrangement of components.
In one embodiment, a computer device is provided, which includes a memory, a processor, and a computer program stored in the memory and executable on the processor, and when the processor executes the computer program, the steps of the reconciliation method in the above embodiment are implemented, for example, in steps 202 to 210 shown in fig. 2, or when the processor executes the computer program, the functions of the modules/units of the reconciliation apparatus in the above embodiment are implemented, for example, the functions of modules 702 to 710 shown in fig. 7. To avoid repetition, the description is omitted here.
In one embodiment, a computer-readable storage medium is provided, on which a computer program is stored, and the computer program, when executed by a processor, implements the steps of the reconciliation method in the above embodiment, for example, the steps 202 to 210 shown in fig. 2, or the processor, when executing the computer program, implements the functions of the modules/units of the reconciliation apparatus in the above embodiment, for example, the functions of the modules 702 to 710 shown in fig. 7. To avoid repetition, the description is omitted here.
It will be understood by those skilled in the art that all or part of the processes of the methods of the above embodiments may be implemented by hardware instructions of a computer program, which may be stored in a non-volatile computer readable storage medium, and when executed, may include the processes of the above embodiments of the methods. Any reference to memory, storage, databases, or other media used in the embodiments provided herein may include non-volatile and/or volatile memory. Non-volatile memory can include read-only memory (ROM), programmable ROM (PROM), electrically Programmable ROM (EPROM), electrically Erasable Programmable ROM (EEPROM), or flash memory. Volatile memory can include Random Access Memory (RAM) or external cache memory. By way of illustration and not limitation, RAM is available in a variety of forms such as Static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double Data Rate SDRAM (DDRSDRAM), enhanced SDRAM (ESDRAM), synchronous Link (Synchlink) DRAM (SLDRAM), rambus (Rambus) direct RAM (RDRAM), direct bused dynamic RAM (DRDRAM), and bused dynamic RAM (RDRAM).
It will be apparent to those skilled in the art that, for convenience and brevity of description, only the above-mentioned division of the functional units and modules is illustrated, and in practical applications, the above-mentioned function distribution may be performed by different functional units and modules according to needs, that is, the internal structure of the apparatus is divided into different functional units or modules to perform all or part of the above-mentioned functions.
The technical features of the above embodiments can be arbitrarily combined, and for the sake of brevity, all possible combinations of the technical features in the above embodiments are not described, however, as long as there is no contradiction between the combinations of the technical features, the technical features should be considered as the scope of the present description.
The above-mentioned embodiments only express several embodiments of the present application, and the description thereof is more specific and detailed, but not construed as limiting the scope of the invention. It should be noted that, for those skilled in the art, without departing from the concept of the present application, several changes, improvements or equivalents of partial technical features may be made, and these changes or substitutions do not make the essence of the same technical solution depart from the spirit and scope of the technical solution of the embodiments of the present invention, and fall into the protection scope of the present application. Therefore, the protection scope of the present patent shall be subject to the appended claims.
Claims (9)
1. A reconciliation method is characterized in that the reconciliation method comprises the following steps:
acquiring an unsettled reconciliation task from a reconciliation database;
acquiring the payment center configuration of a current payment center, and judging the reconciliation type of the reconciliation task according to the payment center configuration;
acquiring a to-be-checked bill from a local database, and performing checking processing on the to-be-checked bill according to the checking type to obtain a checking processing result;
the step of obtaining the account checking bill from the local database, and performing account checking processing on the account checking bill according to the account checking type to obtain an account checking processing result includes:
when the reconciliation type is a contrast reconciliation type, acquiring a third party bill as the to-be-reconciled bill, and analyzing the to-be-reconciled bill to obtain to-be-reconciled data;
acquiring comparison reconciliation data of a corresponding local order, and performing consistency comparison on the to-be-reconciled data and the comparison reconciliation data to obtain a reconciliation processing result;
when the account checking processing result accords with a preset account checking processing result, checking a leveling task processing result of an acceptance mechanism corresponding to the current payment center;
and if the leveling task processing result is that all leveling tasks of the acceptance mechanism are leveled, generating an acceptance mechanism statement, and pushing the acceptance mechanism statement to a private cloud, wherein the generated acceptance mechanism statement is generated according to the data to be leveled.
2. The method of claim 1, wherein the obtaining a to-be-reconciled bill from a local database, and performing reconciled processing on the to-be-reconciled bill according to the reconciled type to obtain a reconciled processing result comprises:
when the reconciliation type is third-party reconciliation, acquiring a third-party bill as a to-be-reconciled bill, and analyzing the to-be-reconciled bill to obtain to-be-reconciled data;
taking the preset account checking processing result as the account checking processing result;
the bill of the generation acceptance mechanism is generated according to the data to be leveled.
3. The method of claim 1, wherein the obtaining a to-be-reconciled bill from a local database, and performing reconciled processing on the to-be-reconciled bill according to the reconciled type to obtain a reconciled processing result comprises:
when the reconciliation type is local reconciliation, acquiring a local order from the local database as the to-be-reconciled bill, and taking the preset reconciliation processing result as the reconciliation processing result;
the generation of the acceptance institution statement is generated based on the local order.
4. The method of claim 1, wherein the obtaining the tie data for the corresponding local order comprises:
inquiring the local order corresponding to the order number of the third party bill from a local database;
and acquiring the contrast leveling data of the inquired local order.
5. The method according to claim 4, wherein the obtaining of the tie-up comparison data of the corresponding local order and the consistency comparison of the to-be-tie-up comparison data and the tie-up comparison data to obtain the reconciliation processing result comprises:
acquiring the to-be-leveled fund amount, the to-be-leveled time and the to-be-leveled order state in the to-be-leveled data;
acquiring the comparison amount, the comparison time and the comparison order state in the comparison flat data;
carrying out consistency comparison on the to-be-compared balance and the comparison amount to obtain an amount comparison result;
carrying out consistency comparison on the to-be-compared time and the comparison time to obtain a time comparison result;
carrying out consistency comparison on the status of the to-be-compared flat orders and the status of the compared orders to obtain a status comparison result;
and integrating the money amount comparison result, the time comparison result and the state comparison result to obtain the reconciliation processing result.
6. The method of claim 1, prior to said retrieving an unsettled tie-out task from a tie-out database, further comprising:
creating a reconciliation task;
and inquiring the unsettled account checking task from the account checking database according to a preset condition.
7. A reconciliation apparatus, characterized in that the reconciliation apparatus comprises:
the acquisition module is used for acquiring the account checking tasks without account checking from the account checking database;
the judging module is used for acquiring the payment center configuration of the current payment center and judging the reconciliation type of the reconciliation task according to the payment center configuration;
the account checking module is used for acquiring an account checking bill to be checked from a local database, and performing account checking processing on the account checking bill to be checked according to the account checking type to obtain an account checking processing result; when the reconciliation type is a reconciliation comparison type, acquiring a third party bill as the billing to be reconciled, analyzing the billing to be reconciled to obtain reconciliation data, acquiring reconciliation comparison data of a corresponding local order, and performing consistency comparison on the reconciliation comparison data and the reconciliation comparison data to obtain a reconciliation processing result;
the checking module is used for checking the reconciliation task processing result of the acceptance mechanism corresponding to the current payment center when the reconciliation processing result meets a preset reconciliation processing result;
and the pushing module is used for generating an acceptance mechanism statement bill and pushing the acceptance mechanism statement bill to a private cloud if the statement of level task processing result indicates that all the statement of level tasks of the acceptance mechanism are in level, wherein the generated acceptance mechanism statement bill is generated according to the data to be leveled.
8. A computer device comprising a memory and a processor, the memory storing a computer program, wherein the processor implements the reconciliation method of any of claims 1-6 when executing the computer program.
9. A computer-readable storage medium, on which a computer program is stored, which computer program, when being executed by a processor, carries out the reconciliation method of any one of claims 1 to 6.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910776689.XA CN110738477B (en) | 2019-08-22 | 2019-08-22 | Account checking method and device, computer equipment and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910776689.XA CN110738477B (en) | 2019-08-22 | 2019-08-22 | Account checking method and device, computer equipment and storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN110738477A CN110738477A (en) | 2020-01-31 |
| CN110738477B true CN110738477B (en) | 2023-04-07 |
Family
ID=69267705
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201910776689.XA Active CN110738477B (en) | 2019-08-22 | 2019-08-22 | Account checking method and device, computer equipment and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN110738477B (en) |
Families Citing this family (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111476651B (en) * | 2020-04-07 | 2023-07-18 | 中国民航信息网络股份有限公司 | Data settlement method and device, storage medium and electronic equipment |
| CN111932255B (en) * | 2020-08-12 | 2023-11-03 | 中国人民银行数字货币研究所 | Method and device for realizing transaction reconciliation based on encrypted currency |
| CN112102055B (en) * | 2020-09-09 | 2024-03-22 | 深圳乐信软件技术有限公司 | Data real-time reconciliation method, device, server and storage medium |
| CN112069260A (en) * | 2020-09-09 | 2020-12-11 | 中国人民银行清算总中心 | Data storage and account checking method and system |
| CN112446697A (en) * | 2020-11-12 | 2021-03-05 | 深圳海付移通科技有限公司 | Account checking method and device, computer equipment and storage medium |
| CN112541750B (en) * | 2020-12-08 | 2023-06-30 | 中国联合网络通信集团有限公司 | Data processing method, device, equipment and computer readable storage medium |
| CN113781190A (en) * | 2021-01-13 | 2021-12-10 | 北京沃东天骏信息技术有限公司 | Bill data processing method, system, computer system and medium |
| CN113157787A (en) * | 2021-04-06 | 2021-07-23 | 中信百信银行股份有限公司 | Accounting processing method and device, electronic equipment and readable storage medium |
Family Cites Families (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20070067240A1 (en) * | 2005-09-19 | 2007-03-22 | George James G | Method, system, and program product for resolving unmatched payments |
| US7809615B2 (en) * | 2008-01-31 | 2010-10-05 | Bill.Com, Inc. | Enhanced automated capture of invoices into an electronic payment system |
| CN107833122A (en) * | 2017-10-17 | 2018-03-23 | 安徽广行通信科技股份有限公司 | A kind of reconciliation processing method |
| CN107798109A (en) * | 2017-11-01 | 2018-03-13 | 深圳市牛鼎丰科技有限公司 | Method, apparatus, computer equipment and the storage medium of reconciliation clearance |
| CN107784574B (en) * | 2017-11-21 | 2021-08-31 | 数贸科技（北京）有限公司 | Account checking processing method and device |
| CN108280754B (en) * | 2018-02-13 | 2021-08-06 | 平安科技（深圳）有限公司 | Routing sub-control account checking method and system |
-
2019
- 2019-08-22 CN CN201910776689.XA patent/CN110738477B/en active Active
Also Published As
| Publication number | Publication date |
|---|---|
| CN110738477A (en) | 2020-01-31 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN110738477B (en) | Account checking method and device, computer equipment and storage medium | |
| CN109034988B (en) | Accounting entry generation method and device | |
| CA2895893C (en) | Searchable data archive | |
| CN112037026A (en) | Automatic abnormal transaction work order processing method, device and system | |
| CN111813827A (en) | Blacklist screening method and device, electronic equipment and storage medium | |
| CN111857888A (en) | Transaction processing method and device | |
| CN113139869A (en) | Credit investigation authorization query processing method and device | |
| US11853579B2 (en) | Systems and methods for providing customer service functionality during portfolio migration downtime | |
| WO2020170187A1 (en) | Large-scale processing of data records with efficient retrieval | |
| CN114565443B (en) | Data processing method, data processing device, computer equipment and storage medium | |
| CN112559646A (en) | Report downloading method and device | |
| CN112367266A (en) | Current limiting method, current limiting device, electronic equipment and computer readable medium | |
| US11290505B1 (en) | Data processing systems for data request routing | |
| US11388264B1 (en) | Data processing systems for data request routing | |
| US11934396B2 (en) | Data reconciliation for big data environments | |
| CN110728566B (en) | Data processing method and device in reimbursement file, computer equipment and storage medium | |
| CN114240593A (en) | Data reconciliation method, apparatus, device, medium, and program product | |
| WO2021072943A1 (en) | Financial data management method and apparatus, computer device and storage medium | |
| CN116151981A (en) | Transaction processing request processing method and device | |
| CN117114727A (en) | Method, device, computer equipment and storage medium for generating product model | |
| CN117439982A (en) | Resource management method, device, computer equipment and storage medium | |
| CN113450197A (en) | Hanging account self-balancing result checking method and device | |
| CN116596654A (en) | Index calculation method, apparatus, computer device, and storage medium | |
| CN113987322A (en) | Index data query method and device, computer equipment and computer program product | |
| OA19113A (en) | Large-scale processing of data records with efficient retrieval. |
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 |